Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 725cf8ebd5efe4729d194e5a3965a631aef5af95e4a004edf48be4c25788451a

Tx prefix hash: a83bd7733f3c56b0a1403c642891adc01a12601168a880cf017eecbcc049eae5
Tx public key: fa1259f64521243ac7e276df3601d254238f8f13b609d6c6b4758ca2bee314dc
Timestamp: 1748780857 Timestamp [UCT]: 2025-06-01 12:27:37 Age [y:d:h:m:s]: 00:171:01:44:57
Block: 1295619 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119952 RingCT/type: yes/0
Extra: 01fa1259f64521243ac7e276df3601d254238f8f13b609d6c6b4758ca2bee314dc02110000000943846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ab141471fd8463ae1a8b862364ff6b42fcf0aa8ca62b7b69b68a647a000ff370 0.600000000000 1783122 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": 1295629, "vin": [ { "gen": { "height": 1295619 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ab141471fd8463ae1a8b862364ff6b42fcf0aa8ca62b7b69b68a647a000ff370" } } ], "extra": [ 1, 250, 18, 89, 246, 69, 33, 36, 58, 199, 226, 118, 223, 54, 1, 210, 84, 35, 143, 143, 19, 182, 9, 214, 198, 180, 117, 140, 162, 190, 227, 20, 220, 2, 17, 0, 0, 0, 9, 67, 132, 109, 102, 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