Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 616d7fe23e40c571aab9c5c16a2c6b662852bed5b25925fb44a9b485405c83f0

Tx prefix hash: 067430dad3d84509de4c279eb07ce9af192f9e856020c4ed0e87891b141064d5
Tx public key: a9e14c672a39a96a422c47fb969a7e0aade207994ad0a7925bbb4b94b7188bd8
Timestamp: 1751241910 Timestamp [UCT]: 2025-06-30 00:05:10 Age [y:d:h:m:s]: 00:137:08:47:16
Block: 1315487 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96353 RingCT/type: yes/0
Extra: 01a9e14c672a39a96a422c47fb969a7e0aade207994ad0a7925bbb4b94b7188bd802110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 424f85738d60d0a3c85fc1fb46b85fda643ddd675de41fbdfe78f39eaf249fdc 0.600000000000 1803142 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": 1315497, "vin": [ { "gen": { "height": 1315487 } } ], "vout": [ { "amount": 600000000, "target": { "key": "424f85738d60d0a3c85fc1fb46b85fda643ddd675de41fbdfe78f39eaf249fdc" } } ], "extra": [ 1, 169, 225, 76, 103, 42, 57, 169, 106, 66, 44, 71, 251, 150, 154, 126, 10, 173, 226, 7, 153, 74, 208, 167, 146, 91, 187, 75, 148, 183, 24, 139, 216, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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