Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51c4e0968e6538b0f23e8d5374a8871626897d88500e3e685f84c230da32ee53

Tx prefix hash: 44f738f835c129dd274450ca6fcd390ab9620a2d9b3916f17251528a724e607a
Tx public key: 8eb8136a67c6d8f4c98e705b0de21d2c44e9203be114510697bfa4bf5577f55e
Timestamp: 1717133522 Timestamp [UCT]: 2024-05-31 05:32:02 Age [y:d:h:m:s]: 00:313:22:02:32
Block: 1033791 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224361 RingCT/type: yes/0
Extra: 018eb8136a67c6d8f4c98e705b0de21d2c44e9203be114510697bfa4bf5577f55e0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f1b359bc76b335cc8e328aed2f6fdadb57972754923b7ef0a5fe3f7d4004307 0.600000000000 1502264 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": 1033801, "vin": [ { "gen": { "height": 1033791 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f1b359bc76b335cc8e328aed2f6fdadb57972754923b7ef0a5fe3f7d4004307" } } ], "extra": [ 1, 142, 184, 19, 106, 103, 198, 216, 244, 201, 142, 112, 91, 13, 226, 29, 44, 68, 233, 32, 59, 225, 20, 81, 6, 151, 191, 164, 191, 85, 119, 245, 94, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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