Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a6b5b5182208fb04ea8b40822c859ac8fe5eadbf549e92243065714a76bd86e

Tx prefix hash: 856b1eb0bf27d8ff3c64caadb6afc4164334f42e8d97a58545ccb7b2e93bb431
Tx public key: fc6af9395e461f333b3dd4aad7bb96e5067a72d3a2fb25d7de3099c9a20e3fa7
Timestamp: 1720154279 Timestamp [UCT]: 2024-07-05 04:37:59 Age [y:d:h:m:s]: 00:170:14:14:43
Block: 1058829 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122115 RingCT/type: yes/0
Extra: 01fc6af9395e461f333b3dd4aad7bb96e5067a72d3a2fb25d7de3099c9a20e3fa702110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0131a471ca648b6edf2847b8e1aeeb30d22fd093ef3099f2d07735703583433a 0.600000000000 1529288 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": 1058839, "vin": [ { "gen": { "height": 1058829 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0131a471ca648b6edf2847b8e1aeeb30d22fd093ef3099f2d07735703583433a" } } ], "extra": [ 1, 252, 106, 249, 57, 94, 70, 31, 51, 59, 61, 212, 170, 215, 187, 150, 229, 6, 122, 114, 211, 162, 251, 37, 215, 222, 48, 153, 201, 162, 14, 63, 167, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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