Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca0d6ee7e59810134f123c58a8c3508222df28ee9546a9c3fe8353376f50e8ce

Tx prefix hash: 0e507809a5d74ef1d530a805e85a76f3c8e074206df540f3c690fe000a584917
Tx public key: 0cc2997f8c2b975e02fece060e108b6d6db838ec1a3af0a296b5d8ed6149222d
Timestamp: 1703355060 Timestamp [UCT]: 2023-12-23 18:11:00 Age [y:d:h:m:s]: 01:331:05:43:28
Block: 919559 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 495592 RingCT/type: yes/0
Extra: 010cc2997f8c2b975e02fece060e108b6d6db838ec1a3af0a296b5d8ed6149222d0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9cd35fb82bc52f97245e10bcd7563759e18bfb283a254c34cccb39f95f98f87 0.600000000000 1377233 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": 919569, "vin": [ { "gen": { "height": 919559 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9cd35fb82bc52f97245e10bcd7563759e18bfb283a254c34cccb39f95f98f87" } } ], "extra": [ 1, 12, 194, 153, 127, 140, 43, 151, 94, 2, 254, 206, 6, 14, 16, 139, 109, 109, 184, 56, 236, 26, 58, 240, 162, 150, 181, 216, 237, 97, 73, 34, 45, 2, 17, 0, 0, 0, 1, 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