Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1eea1edc68021d5237ef9aef3d857fb701a592e96cbad291e5aacaae097c0b7c

Tx prefix hash: 801e20786bd3f33cf73356c81f4751f6af8b58e0dbb39b51b6b88d9a521fe97f
Tx public key: 7bffc8d6db27aee516fc2120a82c31fe26523e97133ace727111da1a3068e382
Timestamp: 1732253221 Timestamp [UCT]: 2024-11-22 05:27:01 Age [y:d:h:m:s]: 00:005:10:49:35
Block: 1159041 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3903 RingCT/type: yes/0
Extra: 017bffc8d6db27aee516fc2120a82c31fe26523e97133ace727111da1a3068e382021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f3fa095778a246830f20aae51d34d9e71a8d9a95c6c6d48c7a2420b4d1736d87 0.600000000000 1644672 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": 1159051, "vin": [ { "gen": { "height": 1159041 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f3fa095778a246830f20aae51d34d9e71a8d9a95c6c6d48c7a2420b4d1736d87" } } ], "extra": [ 1, 123, 255, 200, 214, 219, 39, 174, 229, 22, 252, 33, 32, 168, 44, 49, 254, 38, 82, 62, 151, 19, 58, 206, 114, 113, 17, 218, 26, 48, 104, 227, 130, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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