Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72788d376c7b96a76f9c34e9be660b8ecbe3de8eb02903f3576358946b2bf565

Tx prefix hash: 8d946015267de2b439478a8a751f03ee3e6fc7e5621457e8e754fb5a4baa7b58
Tx public key: 9603a07d6ed83babdfe91dad6ef5106e2dae7e5237ca1d1a28bd9ef89609f8a7
Timestamp: 1673099660 Timestamp [UCT]: 2023-01-07 13:54:20 Age [y:d:h:m:s]: 02:053:14:04:26
Block: 669579 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 559961 RingCT/type: yes/0
Extra: 019603a07d6ed83babdfe91dad6ef5106e2dae7e5237ca1d1a28bd9ef89609f8a7021100000006faf35c9c000000000000000000

1 output(s) for total of 3.710280769000 dcy

stealth address amount amount idx
00: 69e590686cf45fbdf0f9beceeb37b085e7c3e8166ecbad740bb89ab3b0ad81f0 3.710280769000 1110924 of 0

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": 669589, "vin": [ { "gen": { "height": 669579 } } ], "vout": [ { "amount": 3710280769, "target": { "key": "69e590686cf45fbdf0f9beceeb37b085e7c3e8166ecbad740bb89ab3b0ad81f0" } } ], "extra": [ 1, 150, 3, 160, 125, 110, 216, 59, 171, 223, 233, 29, 173, 110, 245, 16, 110, 45, 174, 126, 82, 55, 202, 29, 26, 40, 189, 158, 248, 150, 9, 248, 167, 2, 17, 0, 0, 0, 6, 250, 243, 92, 156, 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