Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f187e40f7b63f3f52c4f78d77c51c765fa7e12fea4f0091217587c05980b4d7c

Tx prefix hash: f9687230a8ef2e4d8f120dda763752a2f9c23cc85a90ab14a1c624eb4c3c0bc8
Tx public key: 85fb0a832c2e9d78cf431d3da21eff16f5c4de353239f9d3d92093ffa30aa840
Timestamp: 1582036388 Timestamp [UCT]: 2020-02-18 14:33:08 Age [y:d:h:m:s]: 05:083:04:52:11
Block: 67582 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1212494 RingCT/type: yes/0
Extra: 0185fb0a832c2e9d78cf431d3da21eff16f5c4de353239f9d3d92093ffa30aa84002110000000456c366d3000000000000000000

1 output(s) for total of 366.499668874000 dcy

stealth address amount amount idx
00: 79462d6bb957f4ea9d6e2a69759be98405780a4585e6bd40b020d7b23a0cc821 366.499668874000 124463 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": 67592, "vin": [ { "gen": { "height": 67582 } } ], "vout": [ { "amount": 366499668874, "target": { "key": "79462d6bb957f4ea9d6e2a69759be98405780a4585e6bd40b020d7b23a0cc821" } } ], "extra": [ 1, 133, 251, 10, 131, 44, 46, 157, 120, 207, 67, 29, 61, 162, 30, 255, 22, 245, 196, 222, 53, 50, 57, 249, 211, 217, 32, 147, 255, 163, 10, 168, 64, 2, 17, 0, 0, 0, 4, 86, 195, 102, 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