Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 160aad416355dff75dc813fc0a0e7dfb02a7db6f29a032379703c63149398399

Tx prefix hash: 55d6e1d92d32922046d87e8b561d458bf533dd22521e600ef2598c2c1cabbc9e
Tx public key: 76d20d6fb503445310c6597726f6049f7aab5561cde9da6cbdb8d1f1164cf0f3
Timestamp: 1723964281 Timestamp [UCT]: 2024-08-18 06:58:01 Age [y:d:h:m:s]: 00:271:07:24:14
Block: 1090426 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193799 RingCT/type: yes/0
Extra: 0176d20d6fb503445310c6597726f6049f7aab5561cde9da6cbdb8d1f1164cf0f3021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 187eca3b2b4e96f40f2171dc6c2edd0de9e8a63982e6c55936d1b802cb8ff261 0.600000000000 1565049 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": 1090436, "vin": [ { "gen": { "height": 1090426 } } ], "vout": [ { "amount": 600000000, "target": { "key": "187eca3b2b4e96f40f2171dc6c2edd0de9e8a63982e6c55936d1b802cb8ff261" } } ], "extra": [ 1, 118, 210, 13, 111, 181, 3, 68, 83, 16, 198, 89, 119, 38, 246, 4, 159, 122, 171, 85, 97, 205, 233, 218, 108, 189, 184, 209, 241, 22, 76, 240, 243, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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