Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4898349b97c2126beccd8eabee93799ac349e3cb9a64c2df7fc035845f9fc54d

Tx prefix hash: 0153c6861f567d2f1bacc9d15aefc94d5414a1d30b1eab69941d777959cd0965
Tx public key: d07302363fd603ec05902476e1a442100d08dbe5c3cec0254ad71f6c96df8d36
Timestamp: 1703293543 Timestamp [UCT]: 2023-12-23 01:05:43 Age [y:d:h:m:s]: 01:345:13:57:24
Block: 919048 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 505860 RingCT/type: yes/0
Extra: 01d07302363fd603ec05902476e1a442100d08dbe5c3cec0254ad71f6c96df8d360211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 68aee7ad3d9cf0c9ae1536595d9c641d6a64de968e44d23264bd8e12a98f54ac 0.600000000000 1376712 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": 919058, "vin": [ { "gen": { "height": 919048 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68aee7ad3d9cf0c9ae1536595d9c641d6a64de968e44d23264bd8e12a98f54ac" } } ], "extra": [ 1, 208, 115, 2, 54, 63, 214, 3, 236, 5, 144, 36, 118, 225, 164, 66, 16, 13, 8, 219, 229, 195, 206, 192, 37, 74, 215, 31, 108, 150, 223, 141, 54, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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