Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78723dea0b45bca0585951d79c85b2dfd209bd40d40d86beca7267d8a68bf1c2

Tx prefix hash: 4a8ec5fc7d76b4c15611c49742ae3979d3594684d51488beb2c22f91e7224f8c
Tx public key: 06c97ba6cbde249b4cca92fcd9a02a7822f125d514beedcca87e1b2ec0335472
Timestamp: 1716185082 Timestamp [UCT]: 2024-05-20 06:04:42 Age [y:d:h:m:s]: 01:005:12:14:14
Block: 1025934 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 264858 RingCT/type: yes/0
Extra: 0106c97ba6cbde249b4cca92fcd9a02a7822f125d514beedcca87e1b2ec033547202110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d46bb282ed7716d53b1e9f1ed539cbf0d3b088ada1d9d09876cb77bb4127acc 0.600000000000 1492739 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": 1025944, "vin": [ { "gen": { "height": 1025934 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d46bb282ed7716d53b1e9f1ed539cbf0d3b088ada1d9d09876cb77bb4127acc" } } ], "extra": [ 1, 6, 201, 123, 166, 203, 222, 36, 155, 76, 202, 146, 252, 217, 160, 42, 120, 34, 241, 37, 213, 20, 190, 237, 204, 168, 126, 27, 46, 192, 51, 84, 114, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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