Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 76d239e050d6921890338cf724f5af00e375edf00a280b1039f33758316a75d7

Tx prefix hash: 0bb60e00362031c066b8eaf4c35a5eef99478b8fb419b2d13780009d237ec8ff
Tx public key: bf5dfa22f08e04a7a2890e68e18317427dc7960658720da0b610c6d60cf69ba1
Timestamp: 1720182932 Timestamp [UCT]: 2024-07-05 12:35:32 Age [y:d:h:m:s]: 00:295:06:23:26
Block: 1059069 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210995 RingCT/type: yes/0
Extra: 01bf5dfa22f08e04a7a2890e68e18317427dc7960658720da0b610c6d60cf69ba10211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 34ea90d94b53481e6ffe7c581cdb4937b81a7eb81fd1408caf9dcc33ae4f382b 0.600000000000 1529530 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": 1059079, "vin": [ { "gen": { "height": 1059069 } } ], "vout": [ { "amount": 600000000, "target": { "key": "34ea90d94b53481e6ffe7c581cdb4937b81a7eb81fd1408caf9dcc33ae4f382b" } } ], "extra": [ 1, 191, 93, 250, 34, 240, 142, 4, 167, 162, 137, 14, 104, 225, 131, 23, 66, 125, 199, 150, 6, 88, 114, 13, 160, 182, 16, 198, 214, 12, 246, 155, 161, 2, 17, 0, 0, 0, 8, 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