Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e1c4946e527cd31b970ee1f238c3f3cbd2b68cb5f127922dadad7a5f332e5bf

Tx prefix hash: e4f53395165ba3dbed4e9188f322cce7495893c22914b5b701778daffd80560a
Tx public key: 395bd80fd4a8e39c6de12f2458d67d1cdd916db6ab71469dd1c33eafeede6171
Timestamp: 1703378755 Timestamp [UCT]: 2023-12-24 00:45:55 Age [y:d:h:m:s]: 01:318:11:06:47
Block: 919758 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 486420 RingCT/type: yes/0
Extra: 01395bd80fd4a8e39c6de12f2458d67d1cdd916db6ab71469dd1c33eafeede617102110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 98a64e6b27f51e7b8cfdc393cb0a47386c73e42d87fbd5dcd624b1b7401e4287 0.600000000000 1377436 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": 919768, "vin": [ { "gen": { "height": 919758 } } ], "vout": [ { "amount": 600000000, "target": { "key": "98a64e6b27f51e7b8cfdc393cb0a47386c73e42d87fbd5dcd624b1b7401e4287" } } ], "extra": [ 1, 57, 91, 216, 15, 212, 168, 227, 156, 109, 225, 47, 36, 88, 214, 125, 28, 221, 145, 109, 182, 171, 113, 70, 157, 209, 195, 62, 175, 238, 222, 97, 113, 2, 17, 0, 0, 0, 1, 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