Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a24a86aaaf39d03ef7c52dcdf38e6743defdda44c0341bfc26e6bbb16359cfb7

Tx prefix hash: 5e99a469866be83a9172f8128c567d6d7efc46e1b8fdc01beee23eda8b9e7d51
Tx public key: f690b45209c899fd06d53f12b0ddd0962dd1667076d5bb86a8e193ecb0be61e8
Timestamp: 1731939605 Timestamp [UCT]: 2024-11-18 14:20:05 Age [y:d:h:m:s]: 00:355:05:30:36
Block: 1156443 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 251421 RingCT/type: yes/0
Extra: 01f690b45209c899fd06d53f12b0ddd0962dd1667076d5bb86a8e193ecb0be61e8021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9857e79cd8a6b0a9ecef0845c06ff0d9ca816dcee68323241b1508c2a67a0c8c 0.600000000000 1642066 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": 1156453, "vin": [ { "gen": { "height": 1156443 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9857e79cd8a6b0a9ecef0845c06ff0d9ca816dcee68323241b1508c2a67a0c8c" } } ], "extra": [ 1, 246, 144, 180, 82, 9, 200, 153, 253, 6, 213, 63, 18, 176, 221, 208, 150, 45, 209, 102, 112, 118, 213, 187, 134, 168, 225, 147, 236, 176, 190, 97, 232, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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