Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 061d815b8db3de95d79f100a3314b165ce663d05c803a63d4f1538d9bc48e69a

Tx prefix hash: eebfca3f23407fff88a9836da35f52100802fd55ebbaddca7f62ef304c946233
Tx public key: 5176722ee53e85156f419fe7d75236b618855d21833cc7f425cee6c0e8f39c2f
Timestamp: 1716445074 Timestamp [UCT]: 2024-05-23 06:17:54 Age [y:d:h:m:s]: 00:338:09:58:28
Block: 1028086 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241892 RingCT/type: yes/0
Extra: 015176722ee53e85156f419fe7d75236b618855d21833cc7f425cee6c0e8f39c2f02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a763f39b0756034770dfdb0b3a10cb8a6c65502755104c5b89f61864fc9da7d2 0.600000000000 1496007 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": 1028096, "vin": [ { "gen": { "height": 1028086 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a763f39b0756034770dfdb0b3a10cb8a6c65502755104c5b89f61864fc9da7d2" } } ], "extra": [ 1, 81, 118, 114, 46, 229, 62, 133, 21, 111, 65, 159, 231, 215, 82, 54, 182, 24, 133, 93, 33, 131, 60, 199, 244, 37, 206, 230, 192, 232, 243, 156, 47, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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