Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b982c55a4899e7a4c4e176c64bb3bb1f61ee0ff8503008cba6c0fb4615b51d3

Tx prefix hash: 5496fc64bef30aca7c9c64dff653c137f92c89368ab04d1f3f77b2175855c88e
Tx public key: afae37304a091faf9c27f1ab7d163ba4d02fae5e427099c986504606ebca30a4
Timestamp: 1714280771 Timestamp [UCT]: 2024-04-28 05:06:11 Age [y:d:h:m:s]: 00:303:16:10:47
Block: 1010136 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217068 RingCT/type: yes/0
Extra: 01afae37304a091faf9c27f1ab7d163ba4d02fae5e427099c986504606ebca30a40211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e79f316af5d3e2be808769f81018b8c4dc6b385009a05128dc420965535de2e8 0.600000000000 1472004 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": 1010146, "vin": [ { "gen": { "height": 1010136 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e79f316af5d3e2be808769f81018b8c4dc6b385009a05128dc420965535de2e8" } } ], "extra": [ 1, 175, 174, 55, 48, 74, 9, 31, 175, 156, 39, 241, 171, 125, 22, 59, 164, 208, 47, 174, 94, 66, 112, 153, 201, 134, 80, 70, 6, 235, 202, 48, 164, 2, 17, 0, 0, 0, 1, 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