Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ced276ba6bf2fbd3a352616af5ef2533ad19a13f20a675c1582a4d8505e3e411

Tx prefix hash: 112d612d86a439f5d6ec22c84a47ffeaeec7e4880aff926ecca652ec7fe1afc9
Tx public key: d5f69b1e16d54b6d432910a686acfe7a46cfd8e79bea5fa3343cf95c85e949d4
Timestamp: 1727802925 Timestamp [UCT]: 2024-10-01 17:15:25 Age [y:d:h:m:s]: 00:112:15:29:04
Block: 1122252 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80484 RingCT/type: yes/0
Extra: 01d5f69b1e16d54b6d432910a686acfe7a46cfd8e79bea5fa3343cf95c85e949d402110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d8bd61b707de63754d621badb570f92f4cfc92d44a4ac016803bb6cdb631daea 0.600000000000 1604661 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": 1122262, "vin": [ { "gen": { "height": 1122252 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d8bd61b707de63754d621badb570f92f4cfc92d44a4ac016803bb6cdb631daea" } } ], "extra": [ 1, 213, 246, 155, 30, 22, 213, 75, 109, 67, 41, 16, 166, 134, 172, 254, 122, 70, 207, 216, 231, 155, 234, 95, 163, 52, 60, 249, 92, 133, 233, 73, 212, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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