Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 980691dab830d307dcb7e7ce4da95aeba51f0bbb684be2dcca1abcac6101ee0f

Tx prefix hash: a7d786112692fb016bda22f3cca4a5a49a09b0cc9771135d9db7636ee16d06e6
Tx public key: bd7c25899df6f84f0f3ce975b1da84eed25f85378284b0ef1e3503ef71d814b9
Timestamp: 1704851448 Timestamp [UCT]: 2024-01-10 01:50:48 Age [y:d:h:m:s]: 01:091:21:06:19
Block: 931954 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326768 RingCT/type: yes/0
Extra: 01bd7c25899df6f84f0f3ce975b1da84eed25f85378284b0ef1e3503ef71d814b90211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0641ef0f3f8e72c61f4b7218f0a3ada23af51d70bbf45a12e743b19cbb819415 0.600000000000 1389864 of 15

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": 931964, "vin": [ { "gen": { "height": 931954 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0641ef0f3f8e72c61f4b7218f0a3ada23af51d70bbf45a12e743b19cbb819415" } } ], "extra": [ 1, 189, 124, 37, 137, 157, 246, 248, 79, 15, 60, 233, 117, 177, 218, 132, 238, 210, 95, 133, 55, 130, 132, 176, 239, 30, 53, 3, 239, 113, 216, 20, 185, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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