Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f22e28c7a41e3c621c9f996e7a03f5d6403e825d4006af5cb82b1f0575cb889

Tx prefix hash: e57a477d159b5c0f192ef4bc2ea2f6a9bca03310a01102db9d53cec6b5b4d1bb
Tx public key: d0d8bc48e03fe116c7fdfcfbed11fb6c787ca04cd4486077d0a7e5b788cd7363
Timestamp: 1722361661 Timestamp [UCT]: 2024-07-30 17:47:41 Age [y:d:h:m:s]: 01:105:10:30:17
Block: 1077131 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333849 RingCT/type: yes/0
Extra: 01d0d8bc48e03fe116c7fdfcfbed11fb6c787ca04cd4486077d0a7e5b788cd736302110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9005ff1e1c9c8ca1d0bc82f83f0bad98a23adea1df3c953453aec3a21277321e 0.600000000000 1549676 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": 1077141, "vin": [ { "gen": { "height": 1077131 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9005ff1e1c9c8ca1d0bc82f83f0bad98a23adea1df3c953453aec3a21277321e" } } ], "extra": [ 1, 208, 216, 188, 72, 224, 63, 225, 22, 199, 253, 252, 251, 237, 17, 251, 108, 120, 124, 160, 76, 212, 72, 96, 119, 208, 167, 229, 183, 136, 205, 115, 99, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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