Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cbbf0c66ce44ab5b9c050f145edd649a1d6a7c106de325687ea05cf47434b44d

Tx prefix hash: 5a9d4e7845066ac249ead5e00005c28fc4f82899dde00a6cecd73ff92bcfa291
Tx public key: 8b44d69be8a42db0bc47f3b86ca6cde3f2cd9287265d169aa71ab2ca0cee1f34
Timestamp: 1762101942 Timestamp [UCT]: 2025-11-02 16:45:42 Age [y:d:h:m:s]: 00:067:03:05:27
Block: 1403474 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 48084 RingCT/type: yes/0
Extra: 018b44d69be8a42db0bc47f3b86ca6cde3f2cd9287265d169aa71ab2ca0cee1f340211000000075dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5817f36cca2816b0f421d5c6c0e80cb90dcc2eeb2cb13c594e892292a6ca5459 0.600000000000 1891821 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": 1403484, "vin": [ { "gen": { "height": 1403474 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5817f36cca2816b0f421d5c6c0e80cb90dcc2eeb2cb13c594e892292a6ca5459" } } ], "extra": [ 1, 139, 68, 214, 155, 232, 164, 45, 176, 188, 71, 243, 184, 108, 166, 205, 227, 242, 205, 146, 135, 38, 93, 22, 154, 167, 26, 178, 202, 12, 238, 31, 52, 2, 17, 0, 0, 0, 7, 93, 251, 190, 42, 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