Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e71e8bd8deea3f216816208edd94db5fd9163a9eba64b9f611a2d64565285a0

Tx prefix hash: 760c44d0ab85ccf1dfe10f70a7abf0fa6f2617d4cbe7476f0605e4e67fc629e7
Tx public key: 434ff612555f2aa9181b6e68272a3d9e7b819fb75313516ebb102f5a7ca5b7ce
Timestamp: 1714567489 Timestamp [UCT]: 2024-05-01 12:44:49 Age [y:d:h:m:s]: 00:345:10:09:37
Block: 1012519 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246927 RingCT/type: yes/0
Extra: 01434ff612555f2aa9181b6e68272a3d9e7b819fb75313516ebb102f5a7ca5b7ce0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 25894fd00e7dd3eeb6ad98cbbc382189c942ade4f9b866f7ab1b04c6f8a99ee4 0.600000000000 1475073 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": 1012529, "vin": [ { "gen": { "height": 1012519 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25894fd00e7dd3eeb6ad98cbbc382189c942ade4f9b866f7ab1b04c6f8a99ee4" } } ], "extra": [ 1, 67, 79, 246, 18, 85, 95, 42, 169, 24, 27, 110, 104, 39, 42, 61, 158, 123, 129, 159, 183, 83, 19, 81, 110, 187, 16, 47, 90, 124, 165, 183, 206, 2, 17, 0, 0, 0, 5, 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