Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68f5db28c73d9609147f102b0f66007d7f6fd742260e1348f6f418b2ec4b2f5e

Tx prefix hash: 19dd5a92726d701162b736fd6c4160aa7249368bf380ee36367d97fc9fbd24eb
Tx public key: 0ba2ad5bb9e128202cbb0be4060f02810dd6662c496f0826a9ef403140e22d1c
Timestamp: 1728910771 Timestamp [UCT]: 2024-10-14 12:59:31 Age [y:d:h:m:s]: 00:168:18:31:23
Block: 1131437 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120391 RingCT/type: yes/0
Extra: 010ba2ad5bb9e128202cbb0be4060f02810dd6662c496f0826a9ef403140e22d1c021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 92cb4cbe4e3b9b113b4b5fb3eaab3a6923a24897e1a1e9f87a734e888b335b59 0.600000000000 1614336 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": 1131447, "vin": [ { "gen": { "height": 1131437 } } ], "vout": [ { "amount": 600000000, "target": { "key": "92cb4cbe4e3b9b113b4b5fb3eaab3a6923a24897e1a1e9f87a734e888b335b59" } } ], "extra": [ 1, 11, 162, 173, 91, 185, 225, 40, 32, 44, 187, 11, 228, 6, 15, 2, 129, 13, 214, 102, 44, 73, 111, 8, 38, 169, 239, 64, 49, 64, 226, 45, 28, 2, 17, 0, 0, 0, 4, 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