Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a81b66fa08eb3aaa76f276b86d1c0baa2d30a3166efca3f807ac1c31350292d7

Tx prefix hash: 01f2f70da9736462c0b25732ae9947055695373bfdabb4df7285bb35a949ecae
Tx public key: f7a4f0df5267e108918739614013e9ea425a268068bbd58c8aaf5b4263bb2e11
Timestamp: 1700042855 Timestamp [UCT]: 2023-11-15 10:07:35 Age [y:d:h:m:s]: 01:101:13:48:26
Block: 892098 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333744 RingCT/type: yes/0
Extra: 01f7a4f0df5267e108918739614013e9ea425a268068bbd58c8aaf5b4263bb2e1102110000000175e3f0e9000000000000000000

1 output(s) for total of 0.679374112000 dcy

stealth address amount amount idx
00: f66cceb71643e35769353782e83626baebb9bda543e18586dfb740327c60cd79 0.679374112000 1348159 of 0

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": 892108, "vin": [ { "gen": { "height": 892098 } } ], "vout": [ { "amount": 679374112, "target": { "key": "f66cceb71643e35769353782e83626baebb9bda543e18586dfb740327c60cd79" } } ], "extra": [ 1, 247, 164, 240, 223, 82, 103, 225, 8, 145, 135, 57, 97, 64, 19, 233, 234, 66, 90, 38, 128, 104, 187, 213, 140, 138, 175, 91, 66, 99, 187, 46, 17, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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