Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55f6b4fb9dc216f4e7cf20c06d19d637b3f6c07a4e193f112f73cc078157f07b

Tx prefix hash: 3654cb4578fdb48d14e15c1ffec27296a95f3ec7421391b4478aebe27b82a481
Tx public key: 54db7b2a768ef8926c13749fca98e110a0d14ae2956f5cedc8c3bb06c16b61b5
Timestamp: 1721400733 Timestamp [UCT]: 2024-07-19 14:52:13 Age [y:d:h:m:s]: 00:300:01:37:07
Block: 1069178 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214391 RingCT/type: yes/0
Extra: 0154db7b2a768ef8926c13749fca98e110a0d14ae2956f5cedc8c3bb06c16b61b502110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 89240b96fb908e803f58aca806040e113623d5c5f81f14e308d745db682d068f 0.600000000000 1540501 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": 1069188, "vin": [ { "gen": { "height": 1069178 } } ], "vout": [ { "amount": 600000000, "target": { "key": "89240b96fb908e803f58aca806040e113623d5c5f81f14e308d745db682d068f" } } ], "extra": [ 1, 84, 219, 123, 42, 118, 142, 248, 146, 108, 19, 116, 159, 202, 152, 225, 16, 160, 209, 74, 226, 149, 111, 92, 237, 200, 195, 187, 6, 193, 107, 97, 181, 2, 17, 0, 0, 0, 7, 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