Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3535b2bbe5728dad38b80ab18ede85d8e2b9cf30347eb8981dfe904645e6e698

Tx prefix hash: e85dc34ea763fd1fdafccce0e25b3d415cb97345ba12b3e3d57c1f36061b9d88
Tx public key: 017072918141d639efa75ea4877491a3cc044ae663b11dcb1a8a432b184ce31c
Timestamp: 1727246424 Timestamp [UCT]: 2024-09-25 06:40:24 Age [y:d:h:m:s]: 01:043:19:52:36
Block: 1117630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289721 RingCT/type: yes/0
Extra: 01017072918141d639efa75ea4877491a3cc044ae663b11dcb1a8a432b184ce31c021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d2f0187fb31b8868c002a56bca31e70e2a9788270599d7cebc9d1720c8e7d82a 0.600000000000 1598537 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": 1117640, "vin": [ { "gen": { "height": 1117630 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d2f0187fb31b8868c002a56bca31e70e2a9788270599d7cebc9d1720c8e7d82a" } } ], "extra": [ 1, 1, 112, 114, 145, 129, 65, 214, 57, 239, 167, 94, 164, 135, 116, 145, 163, 204, 4, 74, 230, 99, 177, 29, 203, 26, 138, 67, 43, 24, 76, 227, 28, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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