Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d3af127e1729957c61cdfed7c58f973e5cd7de5ddf05f48adcdf85729e66a4d

Tx prefix hash: b60eff7aec76389e6626e558453db83da3a311050043eae45b7e0aec94cdaab8
Tx public key: 05e293b17973286f01da5e91b6bd4b87cc051632b04dd5633e8b8500e1b6a90f
Timestamp: 1709362823 Timestamp [UCT]: 2024-03-02 07:00:23 Age [y:d:h:m:s]: 01:250:03:39:05
Block: 969371 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 437503 RingCT/type: yes/0
Extra: 0105e293b17973286f01da5e91b6bd4b87cc051632b04dd5633e8b8500e1b6a90f02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 18d9b0ddb10db28ba697b13c3b65b0f5624c71e2408636c6daa62488d4df5ed9 0.600000000000 1429200 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": 969381, "vin": [ { "gen": { "height": 969371 } } ], "vout": [ { "amount": 600000000, "target": { "key": "18d9b0ddb10db28ba697b13c3b65b0f5624c71e2408636c6daa62488d4df5ed9" } } ], "extra": [ 1, 5, 226, 147, 177, 121, 115, 40, 111, 1, 218, 94, 145, 182, 189, 75, 135, 204, 5, 22, 50, 176, 77, 213, 99, 62, 139, 133, 0, 225, 182, 169, 15, 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