Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fc67fab9ce0112689b8058cddc0c1241c1bc0d3764d6269faca851c393cc955

Tx prefix hash: e65c0905b5d4b79a1c037a7846aa4a44fe41707e0d787aa1793b45498e27667b
Tx public key: 8682e0cd4c683f68f9bf6607e9e2d56f40d8641e5ef733bbbec1bff3653f36fe
Timestamp: 1750253909 Timestamp [UCT]: 2025-06-18 13:38:29 Age [y:d:h:m:s]: 00:155:05:19:51
Block: 1307673 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108757 RingCT/type: yes/0
Extra: 018682e0cd4c683f68f9bf6607e9e2d56f40d8641e5ef733bbbec1bff3653f36fe02110000000325a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 54f3dc95dc2473b484b4de0bc0a16028cd6d27f21296733517acbca4ce11d3ec 0.600000000000 1795284 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": 1307683, "vin": [ { "gen": { "height": 1307673 } } ], "vout": [ { "amount": 600000000, "target": { "key": "54f3dc95dc2473b484b4de0bc0a16028cd6d27f21296733517acbca4ce11d3ec" } } ], "extra": [ 1, 134, 130, 224, 205, 76, 104, 63, 104, 249, 191, 102, 7, 233, 226, 213, 111, 64, 216, 100, 30, 94, 247, 51, 187, 190, 193, 191, 243, 101, 63, 54, 254, 2, 17, 0, 0, 0, 3, 37, 163, 90, 15, 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