Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d4488b6fd98bfa74f884dccdd87b52013c5e4c545a83fc5166f4da8598fd6e3

Tx prefix hash: f7e8bcb0cc5d08ac3739f7a60a6f52af722cd0e67591822e64d2456333188439
Tx public key: c99f051eafe9d160e486ba1d56a09d65398cc435267a6a1bf800f5a70344e3b3
Timestamp: 1681154161 Timestamp [UCT]: 2023-04-10 19:16:01 Age [y:d:h:m:s]: 02:044:14:49:29
Block: 735742 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 554085 RingCT/type: yes/0
Extra: 01c99f051eafe9d160e486ba1d56a09d65398cc435267a6a1bf800f5a70344e3b30211000000015029cbac000000000000000000

1 output(s) for total of 2.239657233000 dcy

stealth address amount amount idx
00: 67a1ccf2ba5580f95845c62ba459a73a99e9ca55e69e52faa859be49ea9fd3db 2.239657233000 1182095 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": 735752, "vin": [ { "gen": { "height": 735742 } } ], "vout": [ { "amount": 2239657233, "target": { "key": "67a1ccf2ba5580f95845c62ba459a73a99e9ca55e69e52faa859be49ea9fd3db" } } ], "extra": [ 1, 201, 159, 5, 30, 175, 233, 209, 96, 228, 134, 186, 29, 86, 160, 157, 101, 57, 140, 196, 53, 38, 122, 106, 27, 248, 0, 245, 167, 3, 68, 227, 179, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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