Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c49a190d64e395f34b144632560fed7f193f6b1f086b01a910c84b39c0a808a2

Tx prefix hash: 843b3d00753ea5d7cca5f2edb46b9ff11f0979de3fe7126a34437cce9ddb429f
Tx public key: 08add6a99b3bdbfae22dba8954f10af3be3ce9fd65830335d8b82d52a1ad1a33
Timestamp: 1703654358 Timestamp [UCT]: 2023-12-27 05:19:18 Age [y:d:h:m:s]: 01:125:23:18:08
Block: 922039 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 351152 RingCT/type: yes/0
Extra: 0108add6a99b3bdbfae22dba8954f10af3be3ce9fd65830335d8b82d52a1ad1a33021100000002ad5694ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 053ff800e01aa5bde60680f42701337ea842aeff7c3ec73fe0f8369d6f992fad 0.600000000000 1379733 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": 922049, "vin": [ { "gen": { "height": 922039 } } ], "vout": [ { "amount": 600000000, "target": { "key": "053ff800e01aa5bde60680f42701337ea842aeff7c3ec73fe0f8369d6f992fad" } } ], "extra": [ 1, 8, 173, 214, 169, 155, 59, 219, 250, 226, 45, 186, 137, 84, 241, 10, 243, 190, 60, 233, 253, 101, 131, 3, 53, 216, 184, 45, 82, 161, 173, 26, 51, 2, 17, 0, 0, 0, 2, 173, 86, 148, 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