Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b83d2ab8028dd6aad687050bc481c0817c1a468aae4b63aebeff4f6d1368bc41

Tx prefix hash: 064288a642c8730ef0fbbdafa0f6d2b0e4ff59f4cb53a38604a7dcb9a95155a1
Tx public key: 2e051197f4135263c9ece11f56084b437e110d1c550e9a51dcd38c95bfb0636b
Timestamp: 1712474273 Timestamp [UCT]: 2024-04-07 07:17:53 Age [y:d:h:m:s]: 01:070:05:36:03
Block: 995134 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311117 RingCT/type: yes/0
Extra: 012e051197f4135263c9ece11f56084b437e110d1c550e9a51dcd38c95bfb0636b02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae05e894cd0fba0f718f687bce87c165d29f9c900ae7603966e9c3ae0e8999cc 0.600000000000 1455538 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": 995144, "vin": [ { "gen": { "height": 995134 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae05e894cd0fba0f718f687bce87c165d29f9c900ae7603966e9c3ae0e8999cc" } } ], "extra": [ 1, 46, 5, 17, 151, 244, 19, 82, 99, 201, 236, 225, 31, 86, 8, 75, 67, 126, 17, 13, 28, 85, 14, 154, 81, 220, 211, 140, 149, 191, 176, 99, 107, 2, 17, 0, 0, 0, 2, 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