Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0984a3946e3bc4bda1d76508d063ef8bcc3d3652e5a2a44ffd80f44908e13669

Tx prefix hash: d6f0f28e34d6138f0a00a0b0b3d06949d643ea4bc5f74bd2bf90c76d5bec4b78
Tx public key: fe0e3676f3e00406556e297918fe566f067fcb43a0c885e503fd100e416f8869
Timestamp: 1739968947 Timestamp [UCT]: 2025-02-19 12:42:27 Age [y:d:h:m:s]: 00:318:01:03:19
Block: 1222636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225152 RingCT/type: yes/0
Extra: 01fe0e3676f3e00406556e297918fe566f067fcb43a0c885e503fd100e416f88690211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f541cf33204f128ab6f32ffb34383769b6646eaf066d00e22d2f50b626a70d87 0.600000000000 1709489 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": 1222646, "vin": [ { "gen": { "height": 1222636 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f541cf33204f128ab6f32ffb34383769b6646eaf066d00e22d2f50b626a70d87" } } ], "extra": [ 1, 254, 14, 54, 118, 243, 224, 4, 6, 85, 110, 41, 121, 24, 254, 86, 111, 6, 127, 203, 67, 160, 200, 133, 229, 3, 253, 16, 14, 65, 111, 136, 105, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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