Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dbf7bec2318539009edebd6f8a837bf11badd46558112f7cdb4f9bcf4873ba2c

Tx prefix hash: fc7f27d30ec14e3535b22d52e713240fe602d8bb618d554fa94e665cb99f1f1f
Tx public key: 0ccbc76a35f2462073bfe85616c5461e7c759f6563adbcdcb106927bb85aaec3
Timestamp: 1735028266 Timestamp [UCT]: 2024-12-24 08:17:46 Age [y:d:h:m:s]: 00:175:08:33:04
Block: 1182035 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125038 RingCT/type: yes/0
Extra: 010ccbc76a35f2462073bfe85616c5461e7c759f6563adbcdcb106927bb85aaec30211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8fe80bf1f252275897cf18488543396f61295029a13444f3bafb5e014d0db9b2 0.600000000000 1668464 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": 1182045, "vin": [ { "gen": { "height": 1182035 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8fe80bf1f252275897cf18488543396f61295029a13444f3bafb5e014d0db9b2" } } ], "extra": [ 1, 12, 203, 199, 106, 53, 242, 70, 32, 115, 191, 232, 86, 22, 197, 70, 30, 124, 117, 159, 101, 99, 173, 188, 220, 177, 6, 146, 123, 184, 90, 174, 195, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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