Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9597c9d41f52a1da8f6db577af478efce3824a0d05555ba309445faf3bdc327b

Tx prefix hash: edfcc4e737b0329a62da55f24c3b725e901e552de2929986f7858540197ea5d2
Tx public key: 703eb0c0a451fc0d06d195a6fbaa74ccdb7b6c95252bd168d88e63afd54b053f
Timestamp: 1706424300 Timestamp [UCT]: 2024-01-28 06:45:00 Age [y:d:h:m:s]: 01:281:07:49:34
Block: 944980 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 459874 RingCT/type: yes/0
Extra: 01703eb0c0a451fc0d06d195a6fbaa74ccdb7b6c95252bd168d88e63afd54b053f02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c028b05b5736024f7b4f968b90a8c39d96cf4356875d570786e187f9db02638c 0.600000000000 1403286 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": 944990, "vin": [ { "gen": { "height": 944980 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c028b05b5736024f7b4f968b90a8c39d96cf4356875d570786e187f9db02638c" } } ], "extra": [ 1, 112, 62, 176, 192, 164, 81, 252, 13, 6, 209, 149, 166, 251, 170, 116, 204, 219, 123, 108, 149, 37, 43, 209, 104, 216, 142, 99, 175, 213, 75, 5, 63, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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