Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 788e8511577d2d0287e544e52033709cbb8323d5662fa732c763d0e3389cf475

Tx prefix hash: 7a3e8538fe30d2571e31597227bd14927b2b0f7f7fa029f6d03fb490f4173b34
Tx public key: d7e813ee1d74ce9f9c904d983db790078d289773e6878852a8217a083a1b0dbe
Timestamp: 1696620801 Timestamp [UCT]: 2023-10-06 19:33:21 Age [y:d:h:m:s]: 01:109:08:40:17
Block: 863931 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 339391 RingCT/type: yes/0
Extra: 01d7e813ee1d74ce9f9c904d983db790078d289773e6878852a8217a083a1b0dbe02110000000775e3f0e9000000000000000000

1 output(s) for total of 0.842284141000 dcy

stealth address amount amount idx
00: 0ee9d78930988fca7a77aea4d397e7a04ee312fd0b6a33c0254cf6ac4495fd94 0.842284141000 1318427 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": 863941, "vin": [ { "gen": { "height": 863931 } } ], "vout": [ { "amount": 842284141, "target": { "key": "0ee9d78930988fca7a77aea4d397e7a04ee312fd0b6a33c0254cf6ac4495fd94" } } ], "extra": [ 1, 215, 232, 19, 238, 29, 116, 206, 159, 156, 144, 77, 152, 61, 183, 144, 7, 141, 40, 151, 115, 230, 135, 136, 82, 168, 33, 122, 8, 58, 27, 13, 190, 2, 17, 0, 0, 0, 7, 117, 227, 240, 233, 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