Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 681d116ad7592ec482ca3586f328c3b4dadf56a54f1699313cb7be64b005b108

Tx prefix hash: 6f405a47f952a9a3b63156d0e54e199ba3fc11a0b3a93f8cebbcfe0e253c9754
Tx public key: 5c2e89ff94db6603c12617145a4391d4f3db62c53d97b4ebbbf2af88f0feabd9
Timestamp: 1689886158 Timestamp [UCT]: 2023-07-20 20:49:18 Age [y:d:h:m:s]: 01:253:16:00:11
Block: 808157 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 442394 RingCT/type: yes/0
Extra: 015c2e89ff94db6603c12617145a4391d4f3db62c53d97b4ebbbf2af88f0feabd9021100000004e6d27f9c000000000000000000

1 output(s) for total of 1.288963131000 dcy

stealth address amount amount idx
00: 156cf58c695f9f2dc242e9cb92adec81e6677eff22adbd58f9692203accf26cb 1.288963131000 1259720 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": 808167, "vin": [ { "gen": { "height": 808157 } } ], "vout": [ { "amount": 1288963131, "target": { "key": "156cf58c695f9f2dc242e9cb92adec81e6677eff22adbd58f9692203accf26cb" } } ], "extra": [ 1, 92, 46, 137, 255, 148, 219, 102, 3, 193, 38, 23, 20, 90, 67, 145, 212, 243, 219, 98, 197, 61, 151, 180, 235, 187, 242, 175, 136, 240, 254, 171, 217, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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