Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02ab22ab336dea5a4c31edbf06ba0c1c07741e109d0eb6ace5e7a8e579be226c

Tx prefix hash: 504e078afc1693972c7c9dd86122ef1f1469457646a7bc10da6790a4dbd14678
Tx public key: a223a914adf9bdb704924e33cfb3d44432894eec9bfbe3752f219cc495af0908
Timestamp: 1583457934 Timestamp [UCT]: 2020-03-06 01:25:34 Age [y:d:h:m:s]: 05:043:04:22:27
Block: 77253 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1185972 RingCT/type: yes/0
Extra: 01a223a914adf9bdb704924e33cfb3d44432894eec9bfbe3752f219cc495af090802110000000d4943cd9f000000000000000000

1 output(s) for total of 340.431341146000 dcy

stealth address amount amount idx
00: 46df5df3b1df9970a2afec56c470e55b943dee9ecb2f7926e592802e7f552627 340.431341146000 142154 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": 77263, "vin": [ { "gen": { "height": 77253 } } ], "vout": [ { "amount": 340431341146, "target": { "key": "46df5df3b1df9970a2afec56c470e55b943dee9ecb2f7926e592802e7f552627" } } ], "extra": [ 1, 162, 35, 169, 20, 173, 249, 189, 183, 4, 146, 78, 51, 207, 179, 212, 68, 50, 137, 78, 236, 155, 251, 227, 117, 47, 33, 156, 196, 149, 175, 9, 8, 2, 17, 0, 0, 0, 13, 73, 67, 205, 159, 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