Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc6617a8f3b2bff85712a4242938fccc928d6985e4f770a1721860c2970bd10c

Tx prefix hash: 7085bdd3beef330c8ae1ff75d497b7de304ab2921394321d20f44759aebd236f
Tx public key: 5ca7a0069ea555081dfaf56c544e06b6e76798a6c87e12942cabe8fb99e19f67
Timestamp: 1711272349 Timestamp [UCT]: 2024-03-24 09:25:49 Age [y:d:h:m:s]: 01:062:06:49:02
Block: 985218 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 305514 RingCT/type: yes/0
Extra: 015ca7a0069ea555081dfaf56c544e06b6e76798a6c87e12942cabe8fb99e19f6702110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a86e4e89274232e9e2a830fcb84da05b39fb38e010b53f569aa673e58dec0abf 0.600000000000 1445427 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": 985228, "vin": [ { "gen": { "height": 985218 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a86e4e89274232e9e2a830fcb84da05b39fb38e010b53f569aa673e58dec0abf" } } ], "extra": [ 1, 92, 167, 160, 6, 158, 165, 85, 8, 29, 250, 245, 108, 84, 78, 6, 182, 231, 103, 152, 166, 200, 126, 18, 148, 44, 171, 232, 251, 153, 225, 159, 103, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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