Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b203f22d8cc005f4f3b16054721dbc21bffbbb85f9e96eb6de5fa98d7710eb5b

Tx prefix hash: 4a143f709e4b4fe832b133951c6aeaeb5de36894e3cbaca591c4cab05a7dea43
Tx public key: 2d68a1c4c312f79ae831ba6c6ba9e5de031e6f4f1cffffd6e5537f7ae5cd4013
Timestamp: 1734288264 Timestamp [UCT]: 2024-12-15 18:44:24 Age [y:d:h:m:s]: 00:184:02:32:56
Block: 1175922 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 131276 RingCT/type: yes/0
Extra: 012d68a1c4c312f79ae831ba6c6ba9e5de031e6f4f1cffffd6e5537f7ae5cd40130211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4af9a33baaab86433e189f4566dc42751f65d0a41d5019261cb1babe8cb22756 0.600000000000 1662249 of 15

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": 1175932, "vin": [ { "gen": { "height": 1175922 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4af9a33baaab86433e189f4566dc42751f65d0a41d5019261cb1babe8cb22756" } } ], "extra": [ 1, 45, 104, 161, 196, 195, 18, 247, 154, 232, 49, 186, 108, 107, 169, 229, 222, 3, 30, 111, 79, 28, 255, 255, 214, 229, 83, 127, 122, 229, 205, 64, 19, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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