Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39236054788773d738a416d03a68ae821223b9c003af05d2eeb0078e085afe7a

Tx prefix hash: e1b550a9c2eaac69db8d2745bd10bc7d37f9759915db11d081dd5632400d0002
Tx public key: 1781ac67d5956d865b35efe31315a5096f1683a4f74408a84ac541fd5e55a401
Timestamp: 1697228305 Timestamp [UCT]: 2023-10-13 20:18:25 Age [y:d:h:m:s]: 01:160:12:19:10
Block: 868966 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 375747 RingCT/type: yes/0
Extra: 011781ac67d5956d865b35efe31315a5096f1683a4f74408a84ac541fd5e55a40102110000000133af99f4000000000000000000

1 output(s) for total of 0.810503596000 dcy

stealth address amount amount idx
00: 4d3bb3c34694c511bfeb94f246d966c9245630a6f5c2d4cbd8999e6476c410f6 0.810503596000 1323793 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": 868976, "vin": [ { "gen": { "height": 868966 } } ], "vout": [ { "amount": 810503596, "target": { "key": "4d3bb3c34694c511bfeb94f246d966c9245630a6f5c2d4cbd8999e6476c410f6" } } ], "extra": [ 1, 23, 129, 172, 103, 213, 149, 109, 134, 91, 53, 239, 227, 19, 21, 165, 9, 111, 22, 131, 164, 247, 68, 8, 168, 74, 197, 65, 253, 94, 85, 164, 1, 2, 17, 0, 0, 0, 1, 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