Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8df6b392383c9dfea9ff9f951d24dbe2064bca006f1455deee45acc7bab87da4

Tx prefix hash: c6719bda96a40936434ae012a5a38e26c3f58e8b514dc5de4b9e6cf83714d128
Tx public key: 232fd87420b87786eea49cd743ed3e3f579a926a9ef2f47d61a58d2d77201dde
Timestamp: 1631728969 Timestamp [UCT]: 2021-09-15 18:02:49 Age [y:d:h:m:s]: 04:046:14:10:07
Block: 334469 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1067334 RingCT/type: yes/0
Extra: 01232fd87420b87786eea49cd743ed3e3f579a926a9ef2f47d61a58d2d77201dde021100000015a272b9cb000000000000000000

1 output(s) for total of 47.837205137000 dcy

stealth address amount amount idx
00: f19257220733357f3370fe4a9ec226d7327ad83e183804000548f13b3717e73e 47.837205137000 689870 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": 334479, "vin": [ { "gen": { "height": 334469 } } ], "vout": [ { "amount": 47837205137, "target": { "key": "f19257220733357f3370fe4a9ec226d7327ad83e183804000548f13b3717e73e" } } ], "extra": [ 1, 35, 47, 216, 116, 32, 184, 119, 134, 238, 164, 156, 215, 67, 237, 62, 63, 87, 154, 146, 106, 158, 242, 244, 125, 97, 165, 141, 45, 119, 32, 29, 222, 2, 17, 0, 0, 0, 21, 162, 114, 185, 203, 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