Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9af38d77cc5a1961d9871ba6bcfc1daf461d72363d777abbe2282dcabc23cc63

Tx prefix hash: 3e97bfc4e199a4daf422c6c37dabd9467c3431c5a67795c46329be719c67b270
Tx public key: 5a82b887ad9757e52e4ffd95f3b60afd7169e44fdc14c12e0785e2d4b055ffd2
Timestamp: 1723009788 Timestamp [UCT]: 2024-08-07 05:49:48 Age [y:d:h:m:s]: 00:262:08:29:48
Block: 1082504 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187419 RingCT/type: yes/0
Extra: 015a82b887ad9757e52e4ffd95f3b60afd7169e44fdc14c12e0785e2d4b055ffd202110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1bdfc1dd1f6b4528ba21cb6b7a18c66c5a9fbeb09e48ac8cd8808aca89c816d7 0.600000000000 1556333 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": 1082514, "vin": [ { "gen": { "height": 1082504 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1bdfc1dd1f6b4528ba21cb6b7a18c66c5a9fbeb09e48ac8cd8808aca89c816d7" } } ], "extra": [ 1, 90, 130, 184, 135, 173, 151, 87, 229, 46, 79, 253, 149, 243, 182, 10, 253, 113, 105, 228, 79, 220, 20, 193, 46, 7, 133, 226, 212, 176, 85, 255, 210, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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