Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31d180c2d65f7c41f50500ecada72a20c8e2bf6b0784600c05cd11f07bb7da97

Tx prefix hash: a8dca69c9a64149e90b254eb4ecc14abd7f306df73ab1fd0fae7918111b8ae4a
Tx public key: 89f3926a00875be3f3d1045d328efb35c92ccdb8b2d11d739974e05867e5140e
Timestamp: 1720048724 Timestamp [UCT]: 2024-07-03 23:18:44 Age [y:d:h:m:s]: 00:276:15:22:11
Block: 1057952 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197654 RingCT/type: yes/0
Extra: 0189f3926a00875be3f3d1045d328efb35c92ccdb8b2d11d739974e05867e5140e0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e36d3791ae512a92f527b79d2dec50edc87c6104add8e7d249b753dd6a7796de 0.600000000000 1528395 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": 1057962, "vin": [ { "gen": { "height": 1057952 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e36d3791ae512a92f527b79d2dec50edc87c6104add8e7d249b753dd6a7796de" } } ], "extra": [ 1, 137, 243, 146, 106, 0, 135, 91, 227, 243, 209, 4, 93, 50, 142, 251, 53, 201, 44, 205, 184, 178, 209, 29, 115, 153, 116, 224, 88, 103, 229, 20, 14, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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