Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df226a88599d0ed5f3109ea8b9a564bf57aea65ac85958d3d84537d4fd44aa5e

Tx prefix hash: d87ec55c07f18e1a3f35f1b81db9cb6397665ca6c13ba38b04a1a8556b763796
Tx public key: 46f877c5bcbf13f8e002a77a48995d7fee820ac44b213be9fd2cdbc1f4ad16c6
Timestamp: 1725100584 Timestamp [UCT]: 2024-08-31 10:36:24 Age [y:d:h:m:s]: 00:085:08:25:47
Block: 1099843 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 61034 RingCT/type: yes/0
Extra: 0146f877c5bcbf13f8e002a77a48995d7fee820ac44b213be9fd2cdbc1f4ad16c6021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7185dbbbf9d0ae22cabcc681aecc3ee33e2d2c4bcd78258d3915aa19e6117fb3 0.600000000000 1575812 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": 1099853, "vin": [ { "gen": { "height": 1099843 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7185dbbbf9d0ae22cabcc681aecc3ee33e2d2c4bcd78258d3915aa19e6117fb3" } } ], "extra": [ 1, 70, 248, 119, 197, 188, 191, 19, 248, 224, 2, 167, 122, 72, 153, 93, 127, 238, 130, 10, 196, 75, 33, 59, 233, 253, 44, 219, 193, 244, 173, 22, 198, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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