Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 764b0961912fc220800db937edf3c5907b13f9e9ba873e6c7cf6bbb2c8f4bfd2

Tx prefix hash: f11b6f1acb3b8511043bc8f9c337c621d080b7ba37943c877aa03b27188959df
Tx public key: 48f279d292c9be12f8246b3a99f5ec52c93a9e968245b02bcf8640074c04e8e6
Timestamp: 1715795360 Timestamp [UCT]: 2024-05-15 17:49:20 Age [y:d:h:m:s]: 00:343:20:10:34
Block: 1022692 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245780 RingCT/type: yes/0
Extra: 0148f279d292c9be12f8246b3a99f5ec52c93a9e968245b02bcf8640074c04e8e602110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1969c4bd68b28baa84cc18b4f0f47ba02f933e86500262a138ba568ac93bbae2 0.600000000000 1487369 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": 1022702, "vin": [ { "gen": { "height": 1022692 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1969c4bd68b28baa84cc18b4f0f47ba02f933e86500262a138ba568ac93bbae2" } } ], "extra": [ 1, 72, 242, 121, 210, 146, 201, 190, 18, 248, 36, 107, 58, 153, 245, 236, 82, 201, 58, 158, 150, 130, 69, 176, 43, 207, 134, 64, 7, 76, 4, 232, 230, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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