Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13bb2d5a486aad215e45b8bb88221aaad8930191304fd803b2f51907356575fa

Tx prefix hash: 65f1b0f6d5bff0d978d48944ca9f68dc45629cd4a25e1b8a7afba8f6f60d5399
Tx public key: 097092685e631d660ca9ed1b3e4ea4520d6b00a826b97f10bcfc31e807035df8
Timestamp: 1608972803 Timestamp [UCT]: 2020-12-26 08:53:23 Age [y:d:h:m:s]: 04:003:04:08:09
Block: 169649 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1015371 RingCT/type: yes/0
Extra: 01097092685e631d660ca9ed1b3e4ea4520d6b00a826b97f10bcfc31e807035df80211000000d7df1e48bb000000000000000000

1 output(s) for total of 168.222121096000 dcy

stealth address amount amount idx
00: 01e69caa9a3d8a9e709963b61e5173d33ae53980e33590a41e3a263b48758fae 168.222121096000 316940 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": 169659, "vin": [ { "gen": { "height": 169649 } } ], "vout": [ { "amount": 168222121096, "target": { "key": "01e69caa9a3d8a9e709963b61e5173d33ae53980e33590a41e3a263b48758fae" } } ], "extra": [ 1, 9, 112, 146, 104, 94, 99, 29, 102, 12, 169, 237, 27, 62, 78, 164, 82, 13, 107, 0, 168, 38, 185, 127, 16, 188, 252, 49, 232, 7, 3, 93, 248, 2, 17, 0, 0, 0, 215, 223, 30, 72, 187, 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