Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 660df9e3df59593cd3e7bbde751060ed834e71d92d7cd26444cc03db87e0ccda

Tx prefix hash: c01aff1bd36bf39440aea966e1a002d6a29507719ade3d67626421f587fb41ff
Tx public key: e3963689622b3b879efc204c5b199489d323a7e87f5d8ae076ca3e81b6cb744a
Timestamp: 1716261367 Timestamp [UCT]: 2024-05-21 03:16:07 Age [y:d:h:m:s]: 00:354:22:51:53
Block: 1026573 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253707 RingCT/type: yes/0
Extra: 01e3963689622b3b879efc204c5b199489d323a7e87f5d8ae076ca3e81b6cb744a0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3c2e15ea991dea39c1da9e916f0ada7291bf0aa9c43d2e33d5843383c980ed1f 0.600000000000 1493728 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": 1026583, "vin": [ { "gen": { "height": 1026573 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c2e15ea991dea39c1da9e916f0ada7291bf0aa9c43d2e33d5843383c980ed1f" } } ], "extra": [ 1, 227, 150, 54, 137, 98, 43, 59, 135, 158, 252, 32, 76, 91, 25, 148, 137, 211, 35, 167, 232, 127, 93, 138, 224, 118, 202, 62, 129, 182, 203, 116, 74, 2, 17, 0, 0, 0, 2, 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