Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b06f4e38d05e67b97b327cd00d493ba50caa49e6ff8f85aa6154e3ab6b416c9

Tx prefix hash: 48983f9eeed13bf5b3d0068ed9e8bd05ac2eb337893b15e73ac5c752b166dde5
Tx public key: 5e7f85b99e02150c39f7d748c3d2bff9a242a2f82a5f329bdac59a7eb66bc610
Timestamp: 1704550610 Timestamp [UCT]: 2024-01-06 14:16:50 Age [y:d:h:m:s]: 01:083:03:40:50
Block: 929451 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320546 RingCT/type: yes/0
Extra: 015e7f85b99e02150c39f7d748c3d2bff9a242a2f82a5f329bdac59a7eb66bc6100211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b4506407205e6d517c4e2986e0a1265dea47222928eadc92046e90dc09998e4e 0.600000000000 1387323 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": 929461, "vin": [ { "gen": { "height": 929451 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b4506407205e6d517c4e2986e0a1265dea47222928eadc92046e90dc09998e4e" } } ], "extra": [ 1, 94, 127, 133, 185, 158, 2, 21, 12, 57, 247, 215, 72, 195, 210, 191, 249, 162, 66, 162, 248, 42, 95, 50, 155, 218, 197, 154, 126, 182, 107, 198, 16, 2, 17, 0, 0, 0, 1, 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