Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b03417168fcd5fa72e7c813594ed159db282de45a5e95e8d5655799d3e80e1c3

Tx prefix hash: e7224b3d608ea8582358775dce88f371f03e68d826bd07dfbaaf385ae3049a83
Tx public key: 3af4916543739dd77cd271dd1f13ba1803bbf8eb9dffd7dda1d9a71fc34cc186
Timestamp: 1578831824 Timestamp [UCT]: 2020-01-12 12:23:44 Age [y:d:h:m:s]: 04:358:17:50:51
Block: 43940 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1145906 RingCT/type: yes/0
Extra: 013af4916543739dd77cd271dd1f13ba1803bbf8eb9dffd7dda1d9a71fc34cc18602110000000b4ac5aa02000000000000000000

1 output(s) for total of 438.944267375000 dcy

stealth address amount amount idx
00: a535d328d4953073e92d6ffac5e5f598bebb8c0922ebf719c17fe8b68bccbdb5 438.944267375000 79774 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": 43950, "vin": [ { "gen": { "height": 43940 } } ], "vout": [ { "amount": 438944267375, "target": { "key": "a535d328d4953073e92d6ffac5e5f598bebb8c0922ebf719c17fe8b68bccbdb5" } } ], "extra": [ 1, 58, 244, 145, 101, 67, 115, 157, 215, 124, 210, 113, 221, 31, 19, 186, 24, 3, 187, 248, 235, 157, 255, 215, 221, 161, 217, 167, 31, 195, 76, 193, 134, 2, 17, 0, 0, 0, 11, 74, 197, 170, 2, 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