Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66ac7291c5395e715bdce9d14fdf122ad9af0197fa848d3dbff14c254313ed5b

Tx prefix hash: 70ef88ecae21cdd486a4807dc2f03e956d9b334e1eb63d371eae33cd11597e1e
Tx public key: 6a04be3ed39d9cefb777a238a16f316cf60f26a7f820c8c98e2933fcc3b11a61
Timestamp: 1708932705 Timestamp [UCT]: 2024-02-26 07:31:45 Age [y:d:h:m:s]: 01:068:01:26:45
Block: 965808 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309664 RingCT/type: yes/0
Extra: 016a04be3ed39d9cefb777a238a16f316cf60f26a7f820c8c98e2933fcc3b11a6102110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4515954b8f19173f24a1b97a49a26dcc1434bb21dee213e6fc7857608abd358b 0.600000000000 1425563 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": 965818, "vin": [ { "gen": { "height": 965808 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4515954b8f19173f24a1b97a49a26dcc1434bb21dee213e6fc7857608abd358b" } } ], "extra": [ 1, 106, 4, 190, 62, 211, 157, 156, 239, 183, 119, 162, 56, 161, 111, 49, 108, 246, 15, 38, 167, 248, 32, 200, 201, 142, 41, 51, 252, 195, 177, 26, 97, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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