Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65e85a8e93a7af88bf6617cc7fc04f5717b57fbde79ba57f03c66d7febcf774c

Tx prefix hash: 29b1a2b94603446c7ae33e850c386be2210449135d9432037fc011b16a31aaa8
Tx public key: 254386d01d2e2ae549a00d654d372011b6926f3e64428a4f456f6b7b37e1a16a
Timestamp: 1707436371 Timestamp [UCT]: 2024-02-08 23:52:51 Age [y:d:h:m:s]: 01:075:16:36:16
Block: 953390 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315162 RingCT/type: yes/0
Extra: 01254386d01d2e2ae549a00d654d372011b6926f3e64428a4f456f6b7b37e1a16a0211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c73babc626b7ddecec7e1b8c0da63de2f78a54e0766e07887dfec08cb710113 0.600000000000 1412590 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": 953400, "vin": [ { "gen": { "height": 953390 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c73babc626b7ddecec7e1b8c0da63de2f78a54e0766e07887dfec08cb710113" } } ], "extra": [ 1, 37, 67, 134, 208, 29, 46, 42, 229, 73, 160, 13, 101, 77, 55, 32, 17, 182, 146, 111, 62, 100, 66, 138, 79, 69, 111, 107, 123, 55, 225, 161, 106, 2, 17, 0, 0, 0, 9, 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