Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2050242e8a17dd959742191d9f9348694d8eeb00a810bf2f8a3227631817d77

Tx prefix hash: 07c3efa4368e4f4a30bd829642b81a8e6be9ac073d354687e263fb8dbd65a7f6
Tx public key: 613a9343a79a797b7824a727f53b5232a526a78d9d3157181959e65b1ba0b6fd
Timestamp: 1716806424 Timestamp [UCT]: 2024-05-27 10:40:24 Age [y:d:h:m:s]: 00:300:19:26:35
Block: 1031097 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214968 RingCT/type: yes/0
Extra: 01613a9343a79a797b7824a727f53b5232a526a78d9d3157181959e65b1ba0b6fd02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: afa6ef95f8e4cbd648a7b7ff1ab9fd9889b0c4e299c38683c4d601967cb2be86 0.600000000000 1499456 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": 1031107, "vin": [ { "gen": { "height": 1031097 } } ], "vout": [ { "amount": 600000000, "target": { "key": "afa6ef95f8e4cbd648a7b7ff1ab9fd9889b0c4e299c38683c4d601967cb2be86" } } ], "extra": [ 1, 97, 58, 147, 67, 167, 154, 121, 123, 120, 36, 167, 39, 245, 59, 82, 50, 165, 38, 167, 141, 157, 49, 87, 24, 25, 89, 230, 91, 27, 160, 182, 253, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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