Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ed09d78e3168c8521ea3d45f1039005b3d31c314040f2003fbf45258c055ebc

Tx prefix hash: c934e6c9f6c70d026610e954a9f7d611fbf5a9bc46c2eef07b383b77a5f4be0c
Tx public key: 5b35326d41d4c61e05f8cc46e224ae5d3eaff1c82b314d11d4e2b9536a63616d
Timestamp: 1763083647 Timestamp [UCT]: 2025-11-14 01:27:27 Age [y:d:h:m:s]: 00:056:15:56:19
Block: 1411617 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40575 RingCT/type: yes/0
Extra: 015b35326d41d4c61e05f8cc46e224ae5d3eaff1c82b314d11d4e2b9536a63616d021100000002d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 737eabba565133c212b2c164227067cb751653d0890be4766f50633ff62dfd05 0.600000000000 1900080 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": 1411627, "vin": [ { "gen": { "height": 1411617 } } ], "vout": [ { "amount": 600000000, "target": { "key": "737eabba565133c212b2c164227067cb751653d0890be4766f50633ff62dfd05" } } ], "extra": [ 1, 91, 53, 50, 109, 65, 212, 198, 30, 5, 248, 204, 70, 226, 36, 174, 93, 62, 175, 241, 200, 43, 49, 77, 17, 212, 226, 185, 83, 106, 99, 97, 109, 2, 17, 0, 0, 0, 2, 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