Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce98bc403521e5aa3e759067ed8232fb55986e3e0b6ad3f585dbf1eb122d8ed3

Tx prefix hash: 433d5af99c5fd449854fb18d916d2f84d948c29ad177c61b4ee5880e4a4ca7cb
Tx public key: f82805440a05fa1d8f099408d813e41950724d9222ddd6a16a37add9c7167dac
Timestamp: 1644636622 Timestamp [UCT]: 2022-02-12 03:30:22 Age [y:d:h:m:s]: 02:280:22:52:47
Block: 436736 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 720076 RingCT/type: yes/0
Extra: 01f82805440a05fa1d8f099408d813e41950724d9222ddd6a16a37add9c7167dac0211000000014a0f5013000000000000000000

1 output(s) for total of 21.925148506000 dcy

stealth address amount amount idx
00: 3a10a8955a1e630fb1f38c91e14f3c1d7e911b9346096c00727b4128bb03d9d9 21.925148506000 848173 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": 436746, "vin": [ { "gen": { "height": 436736 } } ], "vout": [ { "amount": 21925148506, "target": { "key": "3a10a8955a1e630fb1f38c91e14f3c1d7e911b9346096c00727b4128bb03d9d9" } } ], "extra": [ 1, 248, 40, 5, 68, 10, 5, 250, 29, 143, 9, 148, 8, 216, 19, 228, 25, 80, 114, 77, 146, 34, 221, 214, 161, 106, 55, 173, 217, 199, 22, 125, 172, 2, 17, 0, 0, 0, 1, 74, 15, 80, 19, 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