Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a86d0182846bfc28396b363f4bf2c062863d5e76bf127cb88aad59d738e5fcb7

Tx prefix hash: 0108f04034ddf88575617f8d1b76b0181c135ffcd3d5c0fa45f82a979f08a6a2
Tx public key: 21fee6e6b2d6d7f80b866523b1d10e6485007d7197cd14fac57037553baf62cd
Timestamp: 1709404383 Timestamp [UCT]: 2024-03-02 18:33:03 Age [y:d:h:m:s]: 01:109:01:53:18
Block: 969723 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 338861 RingCT/type: yes/0
Extra: 0121fee6e6b2d6d7f80b866523b1d10e6485007d7197cd14fac57037553baf62cd0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 352d5d20cd57006f9f23b739a7a20a51b10419cbb30b20e04f6eb0c061b3cc32 0.600000000000 1429562 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": 969733, "vin": [ { "gen": { "height": 969723 } } ], "vout": [ { "amount": 600000000, "target": { "key": "352d5d20cd57006f9f23b739a7a20a51b10419cbb30b20e04f6eb0c061b3cc32" } } ], "extra": [ 1, 33, 254, 230, 230, 178, 214, 215, 248, 11, 134, 101, 35, 177, 209, 14, 100, 133, 0, 125, 113, 151, 205, 20, 250, 197, 112, 55, 85, 59, 175, 98, 205, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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