Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d61b23491a054153139ab9bfd7fd5a9e402f4f71ee2c14a5eecb91282c2cdb39

Tx prefix hash: e116f7d349995c9040aa996c23af315bb148ef3de2ee0c0c2bfc97ad7989357e
Tx public key: 692d434d071069370ef8a2379d943fccbb8a1224040e99b4866c89c9f19f5a4e
Timestamp: 1705186604 Timestamp [UCT]: 2024-01-13 22:56:44 Age [y:d:h:m:s]: 01:044:11:54:43
Block: 934733 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292864 RingCT/type: yes/0
Extra: 01692d434d071069370ef8a2379d943fccbb8a1224040e99b4866c89c9f19f5a4e0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 52ed99eb85c8ec3ec7c3202eecb822263cd11a80f2222722e2ffd79655498c39 0.600000000000 1392749 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": 934743, "vin": [ { "gen": { "height": 934733 } } ], "vout": [ { "amount": 600000000, "target": { "key": "52ed99eb85c8ec3ec7c3202eecb822263cd11a80f2222722e2ffd79655498c39" } } ], "extra": [ 1, 105, 45, 67, 77, 7, 16, 105, 55, 14, 248, 162, 55, 157, 148, 63, 204, 187, 138, 18, 36, 4, 14, 153, 180, 134, 108, 137, 201, 241, 159, 90, 78, 2, 17, 0, 0, 0, 2, 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