Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 738ec172df7832322949a4639b257561270f966f60fb5dbfdc4c059c67e900fd

Tx prefix hash: 0dbd0b974ff9d4ad881fe57d824bf5b4a219da29a1875a601e3785e86a496f7e
Tx public key: df7cec2e87d8bf14942c0004d067c052299744f546b40cf8ec665dcbf7b95c60
Timestamp: 1713635111 Timestamp [UCT]: 2024-04-20 17:45:11 Age [y:d:h:m:s]: 00:258:06:17:23
Block: 1004780 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184874 RingCT/type: yes/0
Extra: 01df7cec2e87d8bf14942c0004d067c052299744f546b40cf8ec665dcbf7b95c6002110000000a0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ec2f7eccda3eedb005a80b32a00d34f658c98c5f953b2c7e452ae0e89dafe39 0.600000000000 1465354 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1004790, "vin": [ { "gen": { "height": 1004780 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ec2f7eccda3eedb005a80b32a00d34f658c98c5f953b2c7e452ae0e89dafe39" } } ], "extra": [ 1, 223, 124, 236, 46, 135, 216, 191, 20, 148, 44, 0, 4, 208, 103, 192, 82, 41, 151, 68, 245, 70, 180, 12, 248, 236, 102, 93, 203, 247, 185, 92, 96, 2, 17, 0, 0, 0, 10, 0, 17, 5, 91, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8