Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53980dd36d4656aa3184b8506d3bdbbd7aac2f44b956f011fef82d46baa236c7

Tx prefix hash: 0529723f145d50776fa07d7a70f61f8cd28157f97177d8b4c61bb6caf0ae6473
Tx public key: 15134fd74d0923cadce7f3ec5f7588c85bfbfadfd5733c1ad8817fdaa4d35b95
Timestamp: 1736390576 Timestamp [UCT]: 2025-01-09 02:42:56 Age [y:d:h:m:s]: 00:162:21:25:36
Block: 1193308 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116078 RingCT/type: yes/0
Extra: 0115134fd74d0923cadce7f3ec5f7588c85bfbfadfd5733c1ad8817fdaa4d35b9502110000000a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3931e076b5a944f2e626697006a4bfe8d77ca25dc0e5d34e018ab839bea7dc1d 0.600000000000 1679867 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": 1193318, "vin": [ { "gen": { "height": 1193308 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3931e076b5a944f2e626697006a4bfe8d77ca25dc0e5d34e018ab839bea7dc1d" } } ], "extra": [ 1, 21, 19, 79, 215, 77, 9, 35, 202, 220, 231, 243, 236, 95, 117, 136, 200, 91, 251, 250, 223, 213, 115, 60, 26, 216, 129, 127, 218, 164, 211, 91, 149, 2, 17, 0, 0, 0, 10, 0, 127, 151, 138, 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