Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9981751011217cf04ae9e2924015e45eb9338561a38acf14bcbe6456ab3aebb6

Tx prefix hash: f68272effd8b66fab84e633e545cb359465c1e20e048bbdf0236f9316b238c25
Tx public key: 0ace5918de9ab0ecfd6855b825e58aee217807a9870aace0c45d5c4fa5fffdcc
Timestamp: 1581244214 Timestamp [UCT]: 2020-02-09 10:30:14 Age [y:d:h:m:s]: 04:323:15:34:56
Block: 61232 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1123460 RingCT/type: yes/0
Extra: 010ace5918de9ab0ecfd6855b825e58aee217807a9870aace0c45d5c4fa5fffdcc02110000001c7adf42d3000000000000000000

1 output(s) for total of 384.692555423000 dcy

stealth address amount amount idx
00: cfb2a576abbb8541cf80a628d794a73b27f957d1a5928dc25fba7d11735107da 384.692555423000 112840 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": 61242, "vin": [ { "gen": { "height": 61232 } } ], "vout": [ { "amount": 384692555423, "target": { "key": "cfb2a576abbb8541cf80a628d794a73b27f957d1a5928dc25fba7d11735107da" } } ], "extra": [ 1, 10, 206, 89, 24, 222, 154, 176, 236, 253, 104, 85, 184, 37, 229, 138, 238, 33, 120, 7, 169, 135, 10, 172, 224, 196, 93, 92, 79, 165, 255, 253, 204, 2, 17, 0, 0, 0, 28, 122, 223, 66, 211, 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