Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac944ac42a94c3e2db86006d2a2c93dd4af8e26bc44331c7498fc10df0fd2f3b

Tx prefix hash: 7269e892883dfd0f19ab8c38660db7dd123a410ca44c29333bd533ff216c56d0
Tx public key: bda3f1e4a2284c1b817a7885cf32dacb2027d336e8c8ff3730500e4c58b195ec
Timestamp: 1716488996 Timestamp [UCT]: 2024-05-23 18:29:56 Age [y:d:h:m:s]: 00:244:03:24:05
Block: 1028453 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174672 RingCT/type: yes/0
Extra: 01bda3f1e4a2284c1b817a7885cf32dacb2027d336e8c8ff3730500e4c58b195ec02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c64f8536178caa0d41bf609f51672e896b49ef9afc1f80244f41009116f9f71 0.600000000000 1496446 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": 1028463, "vin": [ { "gen": { "height": 1028453 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c64f8536178caa0d41bf609f51672e896b49ef9afc1f80244f41009116f9f71" } } ], "extra": [ 1, 189, 163, 241, 228, 162, 40, 76, 27, 129, 122, 120, 133, 207, 50, 218, 203, 32, 39, 211, 54, 232, 200, 255, 55, 48, 80, 14, 76, 88, 177, 149, 236, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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