Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ef981006c0bc542b2003fee8ea1ab6bcb31993a5cb5b402db72c2c2661a89d8

Tx prefix hash: 124796fb5583614815dc6f7cb1d9b312a17ef532a985e925fc8946f884f195b1
Tx public key: 02db284a1f59361f5ca678bb3ac0e40ec40d9f60fcfc4217d9de5780eb90f1e1
Timestamp: 1721751165 Timestamp [UCT]: 2024-07-23 16:12:45 Age [y:d:h:m:s]: 00:286:17:52:50
Block: 1072061 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204877 RingCT/type: yes/0
Extra: 0102db284a1f59361f5ca678bb3ac0e40ec40d9f60fcfc4217d9de5780eb90f1e1021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 10d3af22b8692a64e8203a70f4e9323bdf9b1d97c4b7de04a044f77292f8acb0 0.600000000000 1544500 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": 1072071, "vin": [ { "gen": { "height": 1072061 } } ], "vout": [ { "amount": 600000000, "target": { "key": "10d3af22b8692a64e8203a70f4e9323bdf9b1d97c4b7de04a044f77292f8acb0" } } ], "extra": [ 1, 2, 219, 40, 74, 31, 89, 54, 31, 92, 166, 120, 187, 58, 192, 228, 14, 196, 13, 159, 96, 252, 252, 66, 23, 217, 222, 87, 128, 235, 144, 241, 225, 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