Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f84f287b2f34225060752afce2e13fc18d14620c6e5b85f494679bf21348d193

Tx prefix hash: 6cff72248dd4826cff309acc55fcf2885863ea6d9dc7ff2503b6023dea22003f
Tx public key: 1f1fe83a74660c2b42fd954690c99e7cfa584b8fc4c8308a38ab1f775e5c3c39
Timestamp: 1735736950 Timestamp [UCT]: 2025-01-01 13:09:10 Age [y:d:h:m:s]: 00:105:20:10:33
Block: 1187893 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75433 RingCT/type: yes/0
Extra: 011f1fe83a74660c2b42fd954690c99e7cfa584b8fc4c8308a38ab1f775e5c3c39021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f020439d7df39da2fb9b000691b1b18673297d5af884e05825d979cf54df4a5 0.600000000000 1674390 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": 1187903, "vin": [ { "gen": { "height": 1187893 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f020439d7df39da2fb9b000691b1b18673297d5af884e05825d979cf54df4a5" } } ], "extra": [ 1, 31, 31, 232, 58, 116, 102, 12, 43, 66, 253, 149, 70, 144, 201, 158, 124, 250, 88, 75, 143, 196, 200, 48, 138, 56, 171, 31, 119, 94, 92, 60, 57, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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