Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dcf236a374ac717a5324a1915d0122bc9accd422edfde4a47868e6d8a25c03dd

Tx prefix hash: d47113a7813472cedd7a0ae649ce9064a2953a2bc758e54386fd4d7cf7f8c8f6
Tx public key: a3e5baea7d1c1867e733d72c2623115c549c1632ea30fff3f71dfb0c4e10e376
Timestamp: 1763707257 Timestamp [UCT]: 2025-11-21 06:40:57 Age [y:d:h:m:s]: 00:069:21:40:26
Block: 1416769 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 49883 RingCT/type: yes/0
Extra: 01a3e5baea7d1c1867e733d72c2623115c549c1632ea30fff3f71dfb0c4e10e37602110000000670609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1b2f01f0bbc27061414c7d97e9ddb44bbdae4aa0a5222e816c48db87461fd94 0.600000000000 1905290 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": 1416779, "vin": [ { "gen": { "height": 1416769 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1b2f01f0bbc27061414c7d97e9ddb44bbdae4aa0a5222e816c48db87461fd94" } } ], "extra": [ 1, 163, 229, 186, 234, 125, 28, 24, 103, 231, 51, 215, 44, 38, 35, 17, 92, 84, 156, 22, 50, 234, 48, 255, 243, 247, 29, 251, 12, 78, 16, 227, 118, 2, 17, 0, 0, 0, 6, 112, 96, 157, 3, 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