Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 214d6fd93f93d9ee59b91996a508b5ccabe6994be0cdd6dca384ac9fc1db713d

Tx prefix hash: 95ec0be756ebce1393d00a4f553a4bc4afbddfeb1122bc170dcfb930d0461cb5
Tx public key: 8d1b0e96ae69c031676e62a5f7dc1ed4c72bcfe067b54a3057f0f0e66859619e
Timestamp: 1633220354 Timestamp [UCT]: 2021-10-03 00:19:14 Age [y:d:h:m:s]: 03:091:14:11:31
Block: 345486 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 842442 RingCT/type: yes/0
Extra: 018d1b0e96ae69c031676e62a5f7dc1ed4c72bcfe067b54a3057f0f0e66859619e02110000000b5410958b000000000000000000

1 output(s) for total of 43.980675305000 dcy

stealth address amount amount idx
00: ee431e8b1dfe94617fac0fab51ed43a30813c62f1480b812300f5d7b1c5ae961 43.980675305000 708696 of 0

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": 345496, "vin": [ { "gen": { "height": 345486 } } ], "vout": [ { "amount": 43980675305, "target": { "key": "ee431e8b1dfe94617fac0fab51ed43a30813c62f1480b812300f5d7b1c5ae961" } } ], "extra": [ 1, 141, 27, 14, 150, 174, 105, 192, 49, 103, 110, 98, 165, 247, 220, 30, 212, 199, 43, 207, 224, 103, 181, 74, 48, 87, 240, 240, 230, 104, 89, 97, 158, 2, 17, 0, 0, 0, 11, 84, 16, 149, 139, 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