Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39f4008ae4cf07ae5481c2cda61324d5f89d29c1bfa6cc8eee35a709cd003e89

Tx prefix hash: bb507f15f82e9b214b09f0479a816c7214066d7a9a008890fba5f6f57df29450
Tx public key: ba92af15c8f6d621078433640ef01237e7c8e5a5200d778fff8d18dbb1260ecc
Timestamp: 1733501299 Timestamp [UCT]: 2024-12-06 16:08:19 Age [y:d:h:m:s]: 00:113:14:42:01
Block: 1169384 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80993 RingCT/type: yes/0
Extra: 01ba92af15c8f6d621078433640ef01237e7c8e5a5200d778fff8d18dbb1260ecc021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e723a98877c4415664384e2c0a05863c13a5b1c453e8540ac0b3e386c599904a 0.600000000000 1655101 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": 1169394, "vin": [ { "gen": { "height": 1169384 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e723a98877c4415664384e2c0a05863c13a5b1c453e8540ac0b3e386c599904a" } } ], "extra": [ 1, 186, 146, 175, 21, 200, 246, 214, 33, 7, 132, 51, 100, 14, 240, 18, 55, 231, 200, 229, 165, 32, 13, 119, 143, 255, 141, 24, 219, 177, 38, 14, 204, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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