Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1374988e7a5a148f398d08177316daea250a0a15df85e7a5eae266d881f6a8ec

Tx prefix hash: 1caf9512e4bcbbe3f69f50e90a4c8144fde0557beebada4cbcc6c655f6f97323
Tx public key: 0529d9724abec46e42afaf0311e8ac4133216c8b84adc2a5d47b48de40786e7b
Timestamp: 1745076916 Timestamp [UCT]: 2025-04-19 15:35:16 Age [y:d:h:m:s]: 00:213:22:39:35
Block: 1264950 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150621 RingCT/type: yes/0
Extra: 010529d9724abec46e42afaf0311e8ac4133216c8b84adc2a5d47b48de40786e7b02110000000c6c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb90313d1dfb61121b0103c2db203d9994294550d3fcaa853e0c3635024bd42c 0.600000000000 1752153 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": 1264960, "vin": [ { "gen": { "height": 1264950 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb90313d1dfb61121b0103c2db203d9994294550d3fcaa853e0c3635024bd42c" } } ], "extra": [ 1, 5, 41, 217, 114, 74, 190, 196, 110, 66, 175, 175, 3, 17, 232, 172, 65, 51, 33, 108, 139, 132, 173, 194, 165, 212, 123, 72, 222, 64, 120, 110, 123, 2, 17, 0, 0, 0, 12, 108, 152, 170, 61, 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