Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fae3794c2b927288f97f200e75d6c6f1eee71771728cc498decb3013f861ef05

Tx prefix hash: 45b16b8208c964f85f346442f7f2e8a142586e6eb2298307c39e8741c2fbf60e
Tx public key: e3a8a8dea0ed8f0fe7e52fa886373091960f73aee72258e9b6163d69c84f5ffc
Timestamp: 1695588668 Timestamp [UCT]: 2023-09-24 20:51:08 Age [y:d:h:m:s]: 01:257:09:57:20
Block: 855372 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 445088 RingCT/type: yes/0
Extra: 01e3a8a8dea0ed8f0fe7e52fa886373091960f73aee72258e9b6163d69c84f5ffc02110000000d4b8f5122000000000000000000

1 output(s) for total of 0.899078331000 dcy

stealth address amount amount idx
00: a86dd3f82f14309ea118f23abf0effd32d1965763aba86d27f96870ec15127d3 0.899078331000 1309390 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": 855382, "vin": [ { "gen": { "height": 855372 } } ], "vout": [ { "amount": 899078331, "target": { "key": "a86dd3f82f14309ea118f23abf0effd32d1965763aba86d27f96870ec15127d3" } } ], "extra": [ 1, 227, 168, 168, 222, 160, 237, 143, 15, 231, 229, 47, 168, 134, 55, 48, 145, 150, 15, 115, 174, 231, 34, 88, 233, 182, 22, 61, 105, 200, 79, 95, 252, 2, 17, 0, 0, 0, 13, 75, 143, 81, 34, 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