Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 066b4554f296a16c5654a4187404e9f6c38f6795740937756e3733aee061613c

Tx prefix hash: fc91b5f6beb6d350fba3fde17de97f6739341c1bfa284b97d06a6087cd8c0ef1
Tx public key: ebf84bfc1aea6a50d58cef4f1db272b35d92f07ce99988c478282080ab84c460
Timestamp: 1711858032 Timestamp [UCT]: 2024-03-31 04:07:12 Age [y:d:h:m:s]: 01:000:14:24:30
Block: 990077 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261366 RingCT/type: yes/0
Extra: 01ebf84bfc1aea6a50d58cef4f1db272b35d92f07ce99988c478282080ab84c4600211000000040011055b000000000000000000

1 output(s) for total of 0.600070000000 dcy

stealth address amount amount idx
00: 747633c7cb07669abd3577cbb1c28f0c225bee3f753fbee185e66c6c64a865d7 0.600070000000 1450397 of 0

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": 990087, "vin": [ { "gen": { "height": 990077 } } ], "vout": [ { "amount": 600070000, "target": { "key": "747633c7cb07669abd3577cbb1c28f0c225bee3f753fbee185e66c6c64a865d7" } } ], "extra": [ 1, 235, 248, 75, 252, 26, 234, 106, 80, 213, 140, 239, 79, 29, 178, 114, 179, 93, 146, 240, 124, 233, 153, 136, 196, 120, 40, 32, 128, 171, 132, 196, 96, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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