Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f60eeccb0bbc89dfdf73b53ea97f6262cab3bd212149bc20c2ca94c8690c7b1

Tx prefix hash: 7bd01f178bf800ccf8a43978122266d7807c43eaf7617c55a433511b1e5862f4
Tx public key: 15d4fc3e575a430d1ed507eb754855a96848e82b11460f9bc696c4a8a427bc7d
Timestamp: 1761467915 Timestamp [UCT]: 2025-10-26 08:38:35 Age [y:d:h:m:s]: 00:090:19:48:10
Block: 1398237 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64839 RingCT/type: yes/0
Extra: 0115d4fc3e575a430d1ed507eb754855a96848e82b11460f9bc696c4a8a427bc7d021100000011df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f3b360ec1e44d0645ecbd23e5cba77a1f3fa1781c06a4476e6eba4bd11c81922 0.600000000000 1886530 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": 1398247, "vin": [ { "gen": { "height": 1398237 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f3b360ec1e44d0645ecbd23e5cba77a1f3fa1781c06a4476e6eba4bd11c81922" } } ], "extra": [ 1, 21, 212, 252, 62, 87, 90, 67, 13, 30, 213, 7, 235, 117, 72, 85, 169, 104, 72, 232, 43, 17, 70, 15, 155, 198, 150, 196, 168, 164, 39, 188, 125, 2, 17, 0, 0, 0, 17, 223, 90, 36, 122, 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