Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8a0fbd79fa53c7b56ebc773f25caed675f54a921ccfd71cdbf66f9f5bdfe001

Tx prefix hash: 1faa0471443abc44676efed192e5deae33aedbed1133303f2e23ffcaa1800534
Tx public key: 0c6009ae1cb9e1047101aa949010e60737b7a6714ff4cf54969bc6a952ed7dcb
Timestamp: 1740209196 Timestamp [UCT]: 2025-02-22 07:26:36 Age [y:d:h:m:s]: 00:315:21:26:34
Block: 1224624 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 223620 RingCT/type: yes/0
Extra: 010c6009ae1cb9e1047101aa949010e60737b7a6714ff4cf54969bc6a952ed7dcb021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e6c9936e50705c31d2e889e1a422b6cef7ec8041d04be56609d0f4c7b01f1ed9 0.600000000000 1711487 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": 1224634, "vin": [ { "gen": { "height": 1224624 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e6c9936e50705c31d2e889e1a422b6cef7ec8041d04be56609d0f4c7b01f1ed9" } } ], "extra": [ 1, 12, 96, 9, 174, 28, 185, 225, 4, 113, 1, 170, 148, 144, 16, 230, 7, 55, 183, 166, 113, 79, 244, 207, 84, 150, 155, 198, 169, 82, 237, 125, 203, 2, 17, 0, 0, 0, 5, 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