Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38c13b57df836074978623c54f9015daf3a8cf5788cfa1cbc1ec4c4f2c09d3ba

Tx prefix hash: bd5b6c73c19a74ced07c85a1ea2849613cfbedde42afcb449bf31240a8244fcd
Tx public key: 1bfd05fc2a98aab0f1f230d796d3dd0cb0452347a0ec2f4e6011e59d0d0f231a
Timestamp: 1702412473 Timestamp [UCT]: 2023-12-12 20:21:13 Age [y:d:h:m:s]: 01:181:07:03:14
Block: 911764 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 390734 RingCT/type: yes/0
Extra: 011bfd05fc2a98aab0f1f230d796d3dd0cb0452347a0ec2f4e6011e59d0d0f231a02110000000233af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cb9378fda7586a456ad83c9fbc185a1e24a07d1dc1f076d8dd781cd79548e352 0.600000000000 1368980 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": 911774, "vin": [ { "gen": { "height": 911764 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cb9378fda7586a456ad83c9fbc185a1e24a07d1dc1f076d8dd781cd79548e352" } } ], "extra": [ 1, 27, 253, 5, 252, 42, 152, 170, 176, 241, 242, 48, 215, 150, 211, 221, 12, 176, 69, 35, 71, 160, 236, 47, 78, 96, 17, 229, 157, 13, 15, 35, 26, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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