Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 043c214e7f0cc313cbf25d992a0aac295d9188b7c13b0f9a9d261b732e51ff65

Tx prefix hash: 3c41f3d142ff5ebb877a70945c85a2797df9c4b80d95d143bdc4cc1ad167e601
Tx public key: e6e702eda7a95edf540f0b7959182aa734b6b5b6efdad21925f75c7c4856299e
Timestamp: 1727182827 Timestamp [UCT]: 2024-09-24 13:00:27 Age [y:d:h:m:s]: 00:120:06:16:55
Block: 1117101 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85949 RingCT/type: yes/0
Extra: 01e6e702eda7a95edf540f0b7959182aa734b6b5b6efdad21925f75c7c4856299e021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 85dc48c73e079a49fb133018f7c8557fbfbde37909a441c457177f3ef8cca360 0.600000000000 1597820 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": 1117111, "vin": [ { "gen": { "height": 1117101 } } ], "vout": [ { "amount": 600000000, "target": { "key": "85dc48c73e079a49fb133018f7c8557fbfbde37909a441c457177f3ef8cca360" } } ], "extra": [ 1, 230, 231, 2, 237, 167, 169, 94, 223, 84, 15, 11, 121, 89, 24, 42, 167, 52, 182, 181, 182, 239, 218, 210, 25, 37, 247, 92, 124, 72, 86, 41, 158, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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