Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2adee0b7fb5e131f38ae64eb009b0ea1919d8a4f700de5033422c78e3e870156

Tx prefix hash: c9635c41f3b195d6a8966356ffac4bd8396a66e82cd0307fb3f4f352ddc24ad2
Tx public key: 321ad1acb6a0730868747c28833ede5fe7d4f92cedf2b71630309c214d800e66
Timestamp: 1643310575 Timestamp [UCT]: 2022-01-27 19:09:35 Age [y:d:h:m:s]: 03:011:08:59:24
Block: 426539 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 787296 RingCT/type: yes/0
Extra: 01321ad1acb6a0730868747c28833ede5fe7d4f92cedf2b71630309c214d800e66021100000003db0c7f64000000000000000000

1 output(s) for total of 23.697336819000 dcy

stealth address amount amount idx
00: 67e4dd0f79f2f29f1ff9ca2ce2d2bfd6e2ddf1e9f3a5487ade4447a4303b0987 23.697336819000 835380 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": 426549, "vin": [ { "gen": { "height": 426539 } } ], "vout": [ { "amount": 23697336819, "target": { "key": "67e4dd0f79f2f29f1ff9ca2ce2d2bfd6e2ddf1e9f3a5487ade4447a4303b0987" } } ], "extra": [ 1, 50, 26, 209, 172, 182, 160, 115, 8, 104, 116, 124, 40, 131, 62, 222, 95, 231, 212, 249, 44, 237, 242, 183, 22, 48, 48, 156, 33, 77, 128, 14, 102, 2, 17, 0, 0, 0, 3, 219, 12, 127, 100, 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