Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e9f0a8ef45dfd5873561a7ba64225789a15d89323726c41f6418a645ea031da

Tx prefix hash: 2b3cd4b0c7fb8a24ad115ee7f08f307657ef8e9e7a22fac1ee14c124b4c4b2bc
Tx public key: 0d441b2a04183a6386baaf4535828c4af5548585b047025f85723ea845d7b57f
Timestamp: 1704960603 Timestamp [UCT]: 2024-01-11 08:10:03 Age [y:d:h:m:s]: 01:086:20:29:07
Block: 932858 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323165 RingCT/type: yes/0
Extra: 010d441b2a04183a6386baaf4535828c4af5548585b047025f85723ea845d7b57f02110000001359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a71a3eb5cd8d809a69ec0cf7eeba4e2968167436b3ecd552decbb18672e68a9 0.600000000000 1390798 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": 932868, "vin": [ { "gen": { "height": 932858 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a71a3eb5cd8d809a69ec0cf7eeba4e2968167436b3ecd552decbb18672e68a9" } } ], "extra": [ 1, 13, 68, 27, 42, 4, 24, 58, 99, 134, 186, 175, 69, 53, 130, 140, 74, 245, 84, 133, 133, 176, 71, 2, 95, 133, 114, 62, 168, 69, 215, 181, 127, 2, 17, 0, 0, 0, 19, 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