Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd981ba215829a2ed5fd4bdecc7c3f3dc55c0bace1355b5a1d9c1998a5cd0a25

Tx prefix hash: 9298e936a8f3ca93f7555c5eebfecc27e01b2242672dd7034b62c4c8eeb420d6
Tx public key: 7974892c9f9dcedf97fb562f5f7ba399e1def46e2d6f967fa1482585bc370689
Timestamp: 1751803216 Timestamp [UCT]: 2025-07-06 12:00:16 Age [y:d:h:m:s]: 00:144:17:52:39
Block: 1319913 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101859 RingCT/type: yes/0
Extra: 017974892c9f9dcedf97fb562f5f7ba399e1def46e2d6f967fa1482585bc370689021100000003dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f06ed6b9e364ff916896066bc1237ab9618ebefad4aa6dfcdfa48f1798a0218 0.600000000000 1807606 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": 1319923, "vin": [ { "gen": { "height": 1319913 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f06ed6b9e364ff916896066bc1237ab9618ebefad4aa6dfcdfa48f1798a0218" } } ], "extra": [ 1, 121, 116, 137, 44, 159, 157, 206, 223, 151, 251, 86, 47, 95, 123, 163, 153, 225, 222, 244, 110, 45, 111, 150, 127, 161, 72, 37, 133, 188, 55, 6, 137, 2, 17, 0, 0, 0, 3, 223, 195, 186, 73, 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