Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06a55236d4cc88a9961e0344dce8437517c0fb8b3c3fb9acb3f352dc2ec49bd5

Tx prefix hash: c5ae34b48578bf89ab892c0d6e300b09eb8defc08abada7e9fbbc73f940d4c11
Tx public key: 70f06288d24a72eddc352b455ce904cf4344c528e9f0150c99fc4e8f37dbfc86
Timestamp: 1764880394 Timestamp [UCT]: 2025-12-04 20:33:14 Age [y:d:h:m:s]: 00:017:07:19:21
Block: 1426523 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 12370 RingCT/type: yes/0
Extra: 0170f06288d24a72eddc352b455ce904cf4344c528e9f0150c99fc4e8f37dbfc86021100000009d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 50eb762765fa64e72257db5de588bbd5626b7e03ae495ed85f59a118fb0ed5b2 0.600000000000 1915214 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": 1426533, "vin": [ { "gen": { "height": 1426523 } } ], "vout": [ { "amount": 600000000, "target": { "key": "50eb762765fa64e72257db5de588bbd5626b7e03ae495ed85f59a118fb0ed5b2" } } ], "extra": [ 1, 112, 240, 98, 136, 210, 74, 114, 237, 220, 53, 43, 69, 92, 233, 4, 207, 67, 68, 197, 40, 233, 240, 21, 12, 153, 252, 78, 143, 55, 219, 252, 134, 2, 17, 0, 0, 0, 9, 214, 225, 157, 124, 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