Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c82f148ddc251c529ae362ad01f671a5820b197954fd3ce0c36f8341b9770049

Tx prefix hash: 4813e892b873480d3ffc40e66cbb98a534b240262ef7e75f3694cb792bbb2c5c
Tx public key: 41635d37d3291706872de4e83cb573ef42f264fe79cfa6e32d8c9b1404ccd804
Timestamp: 1725951939 Timestamp [UCT]: 2024-09-10 07:05:39 Age [y:d:h:m:s]: 00:260:21:16:25
Block: 1106896 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186342 RingCT/type: yes/0
Extra: 0141635d37d3291706872de4e83cb573ef42f264fe79cfa6e32d8c9b1404ccd804021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f9f9ad5267e021bbe55fb17c388434c28b674b74d2b9c51ad9bcf9f5f44e2de 0.600000000000 1584499 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": 1106906, "vin": [ { "gen": { "height": 1106896 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f9f9ad5267e021bbe55fb17c388434c28b674b74d2b9c51ad9bcf9f5f44e2de" } } ], "extra": [ 1, 65, 99, 93, 55, 211, 41, 23, 6, 135, 45, 228, 232, 60, 181, 115, 239, 66, 242, 100, 254, 121, 207, 166, 227, 45, 140, 155, 20, 4, 204, 216, 4, 2, 17, 0, 0, 0, 8, 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